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
Bleadperl v5.25.8-68-g94749a5ed2 breaks MAUKE/Quote-Ref-0.03.tar.gz #15843
Comments
From @andkbisect commit 94749a5 Deprecate non-grapheme string delimiter diagnostics Wide character in print at t/03-unicode.t line 12. perl -V Summary of my perl5 (revision 5 version 25 subversion 9) configuration: Characteristics of this binary (from libperl): -- |
From @jkeenanOn Fri, 27 Jan 2017 07:45:57 GMT, andreas.koenig.7os6VVqR@franz.ak.mind.de wrote:
This test fails because the author has enabled fatalization of warnings in tests. ##### I suspect that in the coming months we will get many BBC reports for fatalization of warnings. They don't (IMO) really constitute blockers for perl-5.26.0. Rather, they indicate what work CPAN authors/maintainers need to do. Should we track such tickets in some way to indicate this status? Thank you very much. |
The RT System itself - Status changed from 'new' to 'open' |
From @andk
> On Fri, 27 Jan 2017 07:45:57 GMT, andreas.koenig.7os6VVqR@franz.ak.mind.de wrote:
> This test fails because the author has enabled fatalization of This can be argued from two sides. C< use warnings FATAL => 'all' > is > ##### > I suspect that in the coming months we will get many BBC reports for > Should we track such tickets in some way to indicate this status? I suppose this is a pumpking question. Because whether something is a -- |
From @khwilliamsonThis is fixed in blead by 6b9660c |
@khwilliamson - Status changed from 'open' to 'resolved' |
From @ilmari"James E Keenan via RT" <perlbug-followup@perl.org> writes:
That's just masking the real error message, which happens to contain a
ilmari@garkbit:~/.cpanm/work/1485526294.17204/Quote-Ref-0.03$ prove -bv t/03-unicode.t This reduces to the following: $ perl5.25.9 -CS -Mutf8 -wE 'say qw bar ' Which is a regression: $ perl5.25.8 -CS -Mutf8 -wE 'say qw foo bar ' In fact it seems like if the opening delimiter is above U+100, any #!/usr/bin/env perl use utf8; my @delims = map { splice @delims, 2, 0, "\N{U+2C2}", "\N{U+2F5}"; # between U+100 and U+1000 print "perl $]\n"; my On perl 5.25.9, we get the following failures: perl 5.025009 While on perl 5.25.8 all is good: $ ~/tmp/delimwtf.pl -- |
Migrated from rt.perl.org#130655 (status was 'resolved')
Searchable as RT130655$
The text was updated successfully, but these errors were encountered: