http://www.perlmonks.org?node_id=1127291


in reply to Strange errors in CPAN modules when running on Windows 8.1

What version of Perl are you using (and what was your previous version)?
perl -v

I looked at Device::Leap on CPAN, and there are many passing tests on recent Perl versions. However, there is only one test in the test suite, and it does nothing more than check that the module can be loaded. So, those runtime warnings you get would never be detected by CPAN Testers.

It is likely you are affected by incompatible changes in a new version of Perl. Check the perldeltas at http://perldoc.perl.org/index-history.html

Replies are listed 'Best First'.
Re^2: Strange errors in CPAN modules when running on Windows 8.1
by schweini (Friar) on May 21, 2015 at 01:55 UTC
    This is perl 5, version 20, subversion 2 (v5.20.2) built for MSWin32-x +64-multi-thread

    I was guessing that some regression is biting me, but from what i saw in the Leap.pm source, nothing strange stood out? $BUFF is well-declared, so why would it stop being that all of a sudden?

    Also, I would hope that something as important as Win32::SerialDevice would pass any tests with any new version of perl?

      $BUFF is well-declared, so why would it stop being that all of a sudden?

      It's still "well-declared".
      The warning is not that it has not been declared, but that it has not been assigned a value:
      C:\>perl -wle "my $x; print $x;" Use of uninitialized value $x in print at -e line 1. C:\>perl -wle "my $x; $x = 17; print $x;" 17
      Cheers,
      Rob