Re^9: Does @{ } copy arrays?

B::Concise lists what opcode flag each letter represents. "M"odifiable is the relevant one here.

Interesting tidbit:

As an optimisation, lvalue subs weren't making arylen as Modifiable.

$ perl -MO=Concise,-exec,f -e'sub f :lvalue { $#a }' 2>&1 | grep av2ar
+ylen
4  <1> av2arylen sK/1
[download]

My patch relied on that flag, so it was buggy. The second patch I mentioned made lvalue subs mark arylen as Modifiable.

Comment on Re^9: Does @{ } copy arrays? Download Code

Replies are listed 'Best First'.
Re^10: Does @{ } copy arrays? by QM (Parson) on Oct 30, 2009 at 14:22 UTC
OK, I think I understand most of those examples. Except `foo($#a)` has me scratching my head. It's marked modifiable, but it's not a reference (at least not obvious to me). Maybe this is the older, darker magic of the aliasing involved with `@_` in subs? (Personally, I avoid coding in such an implicit way, preferring to catch the passed arguments explicitly.) I went back an read most of the thread, and, while much of the discussion was over my head, it seems that those in the know are trying to fix it appropriately (or have already done so). Thanks to all for a mind-expanding discussion. -QM -- Quantum Mechanics: The dreams stuff is made of	[reply] [d/l] [select]
Re^11: Does @{ } copy arrays? by ikegami (Patriarch) on Oct 30, 2009 at 14:55 UTC
Params are passed by reference. The elements of `@_` are aliased to the arguments passed. `>perl -le"sub f { $_[0]=456; } $x=123; f($x); print $x;" 456` [download] `>perl -le"sub f { $_[0]=3; } $#a=2; f($#a); print $#a;" 3` [download] it seems that those in the know are trying to fix it appropriately (or have already done so). I wrote a fix. It was reviewed by Rafael who fixed a big in it and committed it.	[reply] [d/l] [select]