Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upperl -CIO works but equivalent -C3 does not #14748
Comments
From @wolfsageCreated by wolfsage@gmail.comTux found that -C3 stopped working properly in 5.22.0: Tux | $ perl -C3 -E'say "\x{2026}"' -CIO still works though. 22ff313 is the commit between 5.21.9 and 5.21.10 that broke it: [perl #123814] replace grok_atou with grok_atoUV Thanks to Tux, LeoNerd, arc, and Zefram for debugging. (I'll leave it to Zefram to fill in details if he wishes.) Perl Info |
From zefram@fysh.orgThe bug introduced by 22ff313 is in Perl_parse_unicode_opts() in A side effect of the nature of the bug is that a slight variant of the $ perl '-C3 ' -E'say "\x{2026}"' As this is a regression from 5.20, the fix should go into 5.22.1. -zefram |
|
The RT System itself - Status changed from 'new' to 'open' |
From @rjbs* Zefram <zefram@fysh.org> [2015-06-10T12:16:53]
+1 -- |
From @hvdsI'll look at this tomorrow. From the information given, it sounds like it shouldn't be hard to fix. Hugo |
From @hvdsShould be fixed now by 89d84ff, apologies for the bug: [perl #125381] fix -Cnn parsing I'm not particularly familiar with the -Cx options, someone more familiar may wish to check t/run/switchC.t to see if test coverage needs further improvement. Assuming this smokes ok I believe it should be good to cherry-pick for 5.22. Hugo |
|
@hvds - Status changed from 'open' to 'pending release' |
From jvoeckler@sdl.comCreated by jvoeckler@sdl.comI frequently use perl to investigate Unicode code points from the astral $ /opt/perl-5.22.0/bin/perl -C7 -le 'print chr(0x1F340)' $ /opt/perl-5.22.0/bin/perl -CS -le 'print chr(0x1F340)' Please restore the numerical arguments to the -C option. It works fine $ /opt/perl-5.20.2/bin/perl -C7 -le 'print chr(0x1F340)' Perl Info |
From @tonycozOn Wed Nov 25 09:23:09 2015, jvoeckler@sdl.com wrote:
This is a duplicate of 125381, which was fixed in blead in 89d84ff and is was backported to 80a44cc in maint-5.22, so it will be fixed in 5.22.1. Thanks for the report. Tony |
|
The RT System itself - Status changed from 'new' to 'open' |
From zefram@fysh.orgvia RT wrote:
The option actually changes behaviour; it doesn't just turn off warnings.
This does seem to be an unintentional breakage. It changed between commit 22ff313 [perl #123814] replace grok_atou with grok_atoUV As this is a regression from 5.20, the fix should be a candidate for -zefram |
From @steve-m-hayOn Fri Nov 27 08:52:08 2015, zefram@fysh.org wrote:
As Tony already noted, this is already backported to maint-5.22, so will be in 5.22.1 (to be released very soon!). |
|
@mauke - Status changed from 'pending release' to 'resolved' |
Migrated from rt.perl.org#125381 (status was 'resolved')
Searchable as RT125381$