Front page | perl.perl5.porters |
Postings from December 2011
<URL: https://rt.cpan.org/Ticket/Display.html?id=73294 >
On Sat Dec 17 21:15:45 2011, ASG wrote:
> On Thu Dec 15 15:39:14 2011, ANDK wrote:
> > Just a cross reference
> >
> > https://rt.perl.org:443/rt3/Ticket/Display.html?id=106288
> >
> > Sorry for te spam,
>
> Is this considered a problem with the new functionality introduced in
> bleed perl or with List::Gen?
>
> From what I can tell, the problem is originating from line 3334 of
> List/Gen.pm:
>
> local *_ = $from ? $list[-1] :
> $source ? \$source->(undef, scalar @list) :
> \scalar @list;
>
> Any idea what the behavior change in bleed would have done to this? I
> wouldn't think that propagating lvalueness could cause the value to
> become undefined.
Ouch! I think I see what’s happening. Propagating lvalueness to @list is probably making
@list return an AV (the array itself). (That’s the way list assignment works. The rv2av
operator, i.e., @foo or @{...}, flattens the array in rvalue context, but returns the array itself in
lvalue context, as in @foo = ..., or in ref context, as in \@list.)
I’ll try and fix that before 5.15.6.
Thread Previous