Beefy Boxes and Bandwidth Generously Provided by pair Networks
Do you know where your variables are?
 
PerlMonks  

Re^2: Solved: Re: Test::Exception error on Strawberry Perl 5.14.3 ('Bareword "xception" ...') [ Bug in Perl ]

by Anonymous Monk
on Jul 30, 2015 at 00:53 UTC ( #1136817=note: print w/replies, xml ) Need Help??


in reply to Re: Solved: Re: Test::Exception error on Strawberry Perl 5.14.3 ('Bareword "xception" ...') [ Bug in Perl ]
in thread Test::Exception error on Strawberry Perl 5.14.3 ('Bareword "xception" ...')

Eeeew

perl5160delta use and require are no longer affected by the I/O layers active in the caller's scope (enabled by open.pm) [perl #96008].

Bug #96008 for perl5: use and require are affected by the open pragma

  • Comment on Re^2: Solved: Re: Test::Exception error on Strawberry Perl 5.14.3 ('Bareword "xception" ...') [ Bug in Perl ]

Replies are listed 'Best First'.
Re^3: Solved: Re: Test::Exception error on Strawberry Perl 5.14.3 ('Bareword "xception" ...') [ Bug in Perl ]
by 1nickt (Abbot) on Jul 30, 2015 at 16:02 UTC

    Thank you for digging into this. I also learned that 5.14.3 is not officially supported, so I am inclined not to worry about the bug and the test failure.

    I would like to have zero test failures, however, so I am thinking I will change the use open() call to a use if ... statement so it doesn't load under the broken perl/OS combo.


    The way forward always starts with a minimal test.

      I would like to have zero test failures, however, so I am thinking I will change the use open() call to a use if ... statement so it doesn't load under the broken perl/OS combo.

      Naturally you're free to do what you think is best

      but

      why do you even care that STDIN/STDERR/STDOUT are in utf8?

      most windows machines don't show unicode by default unless you do chcp

      test suite shouldn't much care if STD* are utf8, if there is an encoding problem in a failing test, byte information is what is important , not correct drawing/rendering in the local shell

      but if you care just binmode $_, q{:utf8} for *STDIN, *STDOUT, *STDERR;

        if there is an encoding problem in a failing test, byte information is what is important , not correct drawing/rendering in the local shell

        Quite so. I just didn't like the warning about printing a wide character.

        Thanks for your response.


        The way forward always starts with a minimal test.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1136817]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others drinking their drinks and smoking their pipes about the Monastery: (9)
As of 2019-10-22 11:54 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    Notices?