New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PERL_UNICODE doesn't propogate to 'require'd scripts #9867
Comments
From andrew@pimlott.netCreated by andrew@pimlott.netI found that the PERL_UNICODE setting affects the "main" script as expected, To demo, I put basically the same code in t1.pl: open( OUT, ">+out" ) or die $!; and t2.pl: open( OUT, ">out" ) or die $!; and run % PERL_UNICODE=31 perl -w t1.pl Note the warning about t2.pl but not t1.pl. I stumbled across this while trying to figure out why the perl debugger This transcript demonstrates that my stdout is utf8, but the debugger's OUT % PERL_UNICODE=31 perl -debug Loading DB routines from perl5db.pl version 1.3 Enter h or `h h' for help, or `man perldebug' for more help. main::(-e:1): bug ;' called at /usr/share/perl/5.10/perl5db.pl line 638 Andrew Perl Info
|
From @rgs2009/9/10 andrew@pimlott.net (via RT) <perlbug-followup@perl.org>:
PERL_UNICODE is a red herring; if you print ${^UNICODE}, you'll see However, at startup, PERL_UNICODE (or -C) also trigger the setting of This is arguably a bug and PERL_UNICODE should rule in all scopes. Opinions ? -- |
The RT System itself - Status changed from 'new' to 'open' |
From @cowensOn Thu, Sep 10, 2009 at 18:34, Rafael Garcia-Suarez
I use PERL_UNICODE=SDL and had expected it to hold true for everything -- |
Migrated from rt.perl.org#69074 (status was 'open')
Searchable as RT69074$
The text was updated successfully, but these errors were encountered: