-
Notifications
You must be signed in to change notification settings - Fork 539
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
eval( Dumper( 'Latin1' ) ) can result in malformed UTF8 #12066
Comments
From zzbbyy@gmail.comCreated by zzbbyy@gmail.comThis is a bug report for perl from zzbbyy@gmail.com, ----------------------------------------------------------------- use strict; use utf8; use Devel::Peek; my $last = eval( Dumper( "\x{f3}" ) ); done_testing; __OUTPUT__ not ok 1 - eval Perl Info
|
zzbbyy@gmail.com - Status changed from 'new' to 'open' |
zzbbyy@gmail.com - Status changed from 'open' to 'new' |
From willert@gmail.comTaken from https://metacpan.org/module/perlunifaq#Data::Dumper-doesnt- Data::Dumper doesn't restore the UTF8 flag; is it broken? No, Data::Dumper's Unicode abilities are as they should be. There have Adding "utf8::upgrade( $last );" after the eval() line restores the flag |
The RT System itself - Status changed from 'new' to 'open' |
From @cpansproutOn Wed Apr 18 23:25:04 2012, zzbbyy wrote:
The real bug here is that �eval� is respecting the �use utf8� from If you put �use feature "unicode_eval"� or �use v5.15� (�use v5.16� That the parser can produce malformed scalars is a separate bug, not -- Father Chrysostomos |
From @jkeenanOn Thu Apr 19 16:53:05 2012, sprout wrote:
I can confirm that Father C's suggestions work, so the OP's problem is I propose that we close this ticket. If someone wishes to discuss I am taking this ticket for the purpose of closing it in seven days Thank you very much. |
From @jkeenanOn Sun Jan 27 17:58:38 2013, jkeenan wrote:
Hearing no objection in the alloted time, am marking ticket Resolved. Thank you very much. |
@jkeenan - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#112532 (status was 'resolved')
Searchable as RT112532$
The text was updated successfully, but these errors were encountered: