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
Format wrongly recognizes argument line in braces as hash #13306
Comments
From springl-perlbug@bfw-online.deThis is a bug report for perl from Stephan springl The program #!/usr/bin/perl will write The change was introduced by commit 705fe0e, Obviously, the lexer tries to figure out whether to return a HASHBRACK Flags: Site configuration information for perl 5.18.1: Configured by Debian Project at Sun Sep 22 14:25:59 MSZ 2013. Summary of my perl5 (revision 5 version 18 subversion 1) configuration: Locally applied patches: @INC for perl 5.18.1: Environment for perl 5.18.1: |
From @cpansproutOn Tue Sep 24 04:57:09 2013, springl-perlbug@bfw-online.de wrote:
Sorry for the long delay in responding. Yes, this does appear to be a problem. That commit was only intended to fix clearly buggy parsing (including the fact that unambiguous anonymous hash constructors were being treated as blocks). It did not occur to me at the time that it would have this effect. I think the least controversial solution would be to treat { as the beginning of a block when it is the first token in a format argument line (this could be backported to 5.18.3 as well), but I want to see what other perl developers think. -- Father Chrysostomos |
The RT System itself - Status changed from 'new' to 'open' |
From @TuxOn Sat, 18 Jan 2014 06:05:12 -0800, "Father Chrysostomos via RT"
that is what it is documented to be The minimum action here is to add tests to t/write.t to guarantee it -- |
From @cpansproutI thought I had replied, but my reply has not shown up.... So I have to write it again. :-( On Sat Jan 18 08:11:50 2014, hmbrand wrote:
Yes, indeed. I had not noticed.
I have fixed this in f60e676. Does it have your vote for backporting to 5.18? -- Father Chrysostomos |
From @TuxOn Sun, 19 Jan 2014 06:23:00 -0800, "Father Chrysostomos via RT"
Yes -- |
From @khwilliamsonI'm marking this as stalled, to be resolved when we put it into a 5.18 maint release, or decide not to make such a release. It has been fixed in blead |
@khwilliamson - Status changed from 'open' to 'stalled' |
From @cpansproutThe fix was backported to 5.18.4 in commit c38e89e. -- Father Chrysostomos |
The RT System itself - Status changed from 'stalled' to 'open' |
@cpansprout - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#119973 (status was 'resolved')
Searchable as RT119973$
The text was updated successfully, but these errors were encountered: