develooper Front page | perl.perl5.porters | Postings from January 2016

Re: [perl #124368] Perl_sv_2pv_flags: Assertion`((svtype)((sv)->sv_flags & 0xff)) != SVt_PVAV && ((svtype)((sv)->sv_flags &0xff)) != SVt_PVHV && ((svtype)((sv)->sv_flags & 0xff)) != SVt_PVFM' failed

Thread Previous | Thread Next
From:
Ricardo Signes
Date:
January 28, 2016 23:19
Subject:
Re: [perl #124368] Perl_sv_2pv_flags: Assertion`((svtype)((sv)->sv_flags & 0xff)) != SVt_PVAV && ((svtype)((sv)->sv_flags &0xff)) != SVt_PVHV && ((svtype)((sv)->sv_flags & 0xff)) != SVt_PVFM' failed
Message ID:
20160128231855.GD15671@debian
* Dave Mitchell <davem@iabyn.com> [2016-01-19T10:57:17]
> On Mon, May 11, 2015 at 05:29:05PM -0700, Tony Cook via RT wrote:
> > Or we could take /$null/ meaning 'use the last match' out the back and
> > bury it.
> 
> How about we make a distinction between literal //, and /$null/? Then make
> only the latter issue a run-time deprecation warning if $null evaluates to
> the empty string?

So, I bet this was heavily debated back in the year 2011, for #96230... but I
was wrong!  (That's when qr// stopped acting like m//.)

Then I guessed it was debated during the discussion of changing "split / /".
Note that with split, the fix was to make "split /$onespace/" act like
"split / /".  Again, wrong!

In review, though, I think this won't end up being worth it.  Dave's suggestion
(at https://rt.perl.org/Ticket/Display.html?id=124368#txn-1348595 ) seems
sensible, and there's no pressing /need/ to break this behavior, even if it has
occasionally seemed more trouble than it's worth.

-- 
rjbs

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About