I'm talking about what happens when return @array; gets run. return @array; is not implemented using XS macros.
And Perl has special handling for dealing with (just) XS code that behaves badly and returns more than one item when called in a scalar context (I even mentioned this specifically previously -- probably in a prior thread about this ever-returning topic but one I re-read recently).
but somehow I find it unlikely
Yeah, I just make all this stuff up. For Python's sake, just go look at the source code if you think I don't know what I'm talking about. Wow, cling much?
Here, the array IS returned from the function :)
Um, actually, a single reference is returned from the function and the fact that the function was predeclared :lvalue means that the caller adds code to dereference that reference. But nice last stab at trying to cling just a little more. q-:
- tye
In reply to Re^11: Confused as to why the "casting context" is mis-behaving (clinging)
by tye
in thread Confused as to why the "casting context" is mis-behaving
by kiz
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |