Re^3: A list assignment gotcha (Updated)

> A bit trickier than I originally thought.

I was about to update that one needs :lvalue and returning a tied scalar then.

Surprised you made it without tie , my last use case must have been different than. :)

> You can use [3, 2, 1] on the RHS, as well.

Nice! :)

> on both the listifier and constructor.

Genius!!! that's how you avoided using Tie::Scalar! :)

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery}

Comment on Re^3: A list assignment gotcha (Updated) Download Code

Replies are listed 'Best First'.
Re^4: A list assignment gotcha (Updated) by jcb (Parson) on Jul 31, 2020 at 01:32 UTC
Great work by both of you, and the possible syntax tricks nicely show TIMTOWTDI, but the original motive for trying `LIST += LIST` was a hoped-for performance gain from the interpreter completing the whole set in one opcode, instead of `add...add...add...`. I suspect that overloaded objects like this will cause problems if used in inner loops. :-) Neat tricks, though...	[reply] [d/l]
Re^5: A list assignment gotcha (Updated) by LanX (Saint) on Jul 31, 2020 at 02:20 UTC
> will cause problems if used in inner loops performance won't be great unless implemented in XS. But that's the way I would implement new features in Perl. a nice syntactic sugar which does the job in pure Perl and stays fully backwards compatible. speed it up in XS for newer versions if it becomes popular, consider including it into CORE. Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery}	[reply]
Re^6: A list assignment gotcha (Updated) by jcb (Parson) on Aug 01, 2020 at 02:10 UTC
Even with an XS implementation, you will still have the dispatch overhead for the overloaded operator. Eventually including it in core perl would allow the parser to resolve the dispatch at compile-time, but until then I wonder how long the list needs to be to make up that difference?	[reply]
Re^7: A list assignment gotcha (Speed) by LanX (Saint) on Aug 01, 2020 at 09:26 UTC


Clear questions and runnable code get the best and fastest answer
	PerlMonks