Front page | perl.perl5.porters |
Postings from April 2013
On 4/22/13 8:09 PM, Ricardo SIGNES via RT wrote:
> On Wed Apr 17 11:51:24 2013, schwern wrote:
>> So I guess we're stuck with this behavior. I propose three things.
>
> Does this mean that you believe this is not blocking 5.18.0? I agree that it's icky and it would be
> nice to have some sane means to get what we want, whether it's fixing the code or adding
> something new. If this is a misfeature and not a regression, though, we're okay to ship like this,
> right-o?
I would like to see the warning and top level mistake fixed. That is a
clear regression. The rest can wait.
$ perl -wle 'use Carp; print Carp::longmess("Foo")'
Foo at -e line 1.
$ perlbrew use perl-5.17.10
$ perl -wle 'use Carp; print Carp::longmess("Foo")'
Use of uninitialized value in concatenation (.) or string at
/Users/schwern/perl5/perlbrew/perls/perl-5.17.10/lib/5.17.10/Carp.pm
line 307.
Use of uninitialized value in concatenation (.) or string at
/Users/schwern/perl5/perlbrew/perls/perl-5.17.10/lib/5.17.10/Carp.pm
line 307.
Foo at line .
Let me poke at it again now.
Thread Next