-
Notifications
You must be signed in to change notification settings - Fork 561
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
Unicode handling of warnings appears broken in 5.18.2 and 5.24.0 #15469
Comments
From [email protected]$ perl -C x.pl say q« foo4 » ; Expected: Or at least an error about the use of an invalid punctuation character as a Also tried this under 5.24.0 and got the same output. -- |
From @cpansproutOn Fri Jul 22 10:36:25 2016, ajs wrote:
The same bug occurs with the ‘(Might be a runaway multi-line...)’ hint that sometimes accompanies a syntax error. In a utf-8 terminal, with 5.12.4: $ perl -CS -e 'use utf8; q Ω' -e 'Ω >' And 5.25.3: $ ./perl -Ilib -CS -e 'use utf8; q Ω' -e 'Ω >' Ow! (Another thing I might note is that the runaway quote hint should include the operator if the delimiter is non-standard, because this is unhelpful: $ perl -e 'q x' -e 'x >' Father Chrysostomos |
The RT System itself - Status changed from 'new' to 'open' |
From @cpansproutOn Tue Jul 26 00:04:19 2016, sprout wrote:
This is fixed in cb65013. But there are problems with heredoc terminators (handled by the same code, more or less), so there is still some more fixing to do: $ ./perl -Ilib -CS -e 'use utf8; <<"«"'
That is not yet fixed.
Neither is that. -- Father Chrysostomos |
From @cpansproutOn Tue Jul 26 01:55:10 2016, sprout wrote:
That one is fixed now in commit 7f7f7d0.
Actually, cb65013 *did* fix it. I didn’t realise that Perl_sv_catpvf supports %c with numbers > 255, but apparently it does. However, it only goes up to 32 bits (at least on a Mac), because %c takes an int (which is 32 bits). That means you get garbled output for heredoc delimiters above \x{7fffffff}, but those are not valid Unicode characters anyway, and hence cannot display in a terminal. So I’m not going to worry about it. (I started to write a patch, but it adds to much complexity to the code.)
I have decided to leave this alone. It’s not easy to fix, and nobody has complained about it. -- Father Chrysostomos |
@cpansprout - Status changed from 'open' to 'pending release' |
From @khwilliamsonThank you for filing this report. You have helped make Perl better. With the release today of Perl 5.26.0, this and 210 other issues have been Perl 5.26.0 may be downloaded via: If you find that the problem persists, feel free to reopen this ticket. |
@khwilliamson - Status changed from 'pending release' to 'resolved' |
Migrated from rt.perl.org#128701 (status was 'resolved')
Searchable as RT128701$
The text was updated successfully, but these errors were encountered: