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


in reply to Re^2: Perl 5.8.? and ParseExcel
in thread Perl 5.8.? and ParseExcel

Perl's implementation of unicode changed quite a lot between 5.6.x and 5.8.x. It is, so I read, very much improved in 5.8.x but with that improvement came the need for a few non-backwards compatible changes and some extra warnings it seems. I've yet done precious little with it.


Examine what is said, not who speaks.
"Efficiency is intelligent laziness." -David Dunham
"Think for yourself!" - Abigail
"Memory, processor, disk in that order on the hardware side. Algorithm, algoritm, algorithm on the code side." - tachyon

Replies are listed 'Best First'.
Re^4: Perl 5.8.? and ParseExcel
by sth (Priest) on Jul 20, 2004 at 20:39 UTC

    -Thanks for the replies BrowserUk. Right now I put in a hack until I can figure out or find an answer,

    { local *STDERR; open(STDERR, '>/dev/null'); $oBook = $oExcel->Parse($disclaimer) || die "Unable to parse $ +disclaimer"; }

    ..not the right solution, but it works for now.

    Thanks Again, sth

      Pragmatic! You could also do:

      { local $SIG{ __WARN__ } = sub{}; $oBook = $oExcel->Parse($disclaimer) || die "Unable to parse $disclaimer"; }

      ps. Dropping a line to the module owner might be good too.


      Examine what is said, not who speaks.
      "Efficiency is intelligent laziness." -David Dunham
      "Think for yourself!" - Abigail
      "Memory, processor, disk in that order on the hardware side. Algorithm, algoritm, algorithm on the code side." - tachyon

        { local $SIG{ __WARN__ } = sub{}; $oBook = $oExcel->Parse($disclaimer) || die "Unable to parse $disclaimer"; }

        ..thanks, I like this better. :-)

        ps. Dropping a line to the module owner might be good too.

        ...I was thinking that myself.

        Once again Thanks,

        sth