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
Inconsistent treatment of nulls and newlines in <...> #12488
Comments
From @cpansproutThis one fails: eval "<\n>; 1" or print $@; This one succeeds in perl, but not miniperl (because miniperl calls sh, which doesn’t like the null): eval "<\0\n>; 1" or print $@; This one fails (it has to be in a sring eval to work): perl -e 'print "<\0\n>"' | perl -MO=Deparse Flags: Site configuration information for perl 5.17.5: Configured by sprout at Sat Sep 22 18:51:23 PDT 2012. Summary of my perl5 (revision 5 version 17 subversion 5) configuration: Locally applied patches: @INC for perl 5.17.5: Environment for perl 5.17.5: |
From @jkeenanOn Sun Oct 14 13:09:47 2012, sprout wrote:
Is this the failure you are referring to: ##### |
The RT System itself - Status changed from 'new' to 'open' |
From @cpansproutOn Oct 14, 2012, at 5:54 PM, James E Keenan via RT wrote:
Yes, but you can sneak past it with a null, *if* it is inside a string eval. |
From zefram@fysh.orgLeaving aside miniperl, which doesn't matter, the -zefram |
@iabyn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#115252 (status was 'resolved')
Searchable as RT115252$
The text was updated successfully, but these errors were encountered: