Re^4: Perl v5.13.7 is released

Given time, I expect we'll be able to push $arref1, $arref2

I don't think so (if you expect that would be equivalent to push $arref1, @$arref2), because it's ambiguous (do you want to push the ref $arref2 itself or the array's elements?), while the current change isn't. Only the programmer can resolve that ambiguity...

Comment on Re^4: Perl v5.13.7 is released Select or Download Code

Replies are listed 'Best First'.
Re^5: Perl v5.13.7 is released by syphilis (Archbishop) on Nov 24, 2010 at 08:39 UTC
Only the programmer can resolve that ambiguity Hmph ... so much for perl's fabled DWIM capabilities !!! ;-) Cheers, Rob	[reply]
Re^5: Perl v5.13.7 is released by talexb (Chancellor) on Nov 25, 2010 at 15:43 UTC
(do you want to push the ref `$arref2` itself or the array's elements?) Interesting point, but wrong, I think. The change that 5.13.7 introduces only affects the first argument of a `push`; subsequent arguments behave as before. Alex / talexb / Toronto "Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds	[reply] [d/l] [select]
Re^6: Perl v5.13.7 is released by Anonymous Monk on Nov 25, 2010 at 16:21 UTC
The change that 5.13.7 introduces only affects the first argument... That's all clear, but I understood syphilis to be talking about a hypothetical future extension of "`$arref` means `@$arref`" to the second argument, too. Otherwise why would he have said "Given time, I expect we'll be able to..." if it applies to what is possible already? But maybe I got him wrong.	[reply] [d/l] [select]