Re^4: Splitting array into two with a regex

@{$rec->vals()} is an expression that returns a list.

Well, technically, it's an lvalue array expression, which when used as an rvalue in a list context, returns a list. When its used in a scalar context, it returns the length of the list. When it's used as an lvalue, it's an array.

-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.

Comment on Re^4: Splitting array into two with a regex Download Code

Replies are listed 'Best First'.
Re^5: Splitting array into two with a regex by ikegami (Patriarch) on Nov 08, 2005 at 19:17 UTC
Can you back that up? I can't find any way of using it as an lvalue. Everything I tried gave me a count (in scalar context) or a list (in list context). Some tests: Read more... (2 kB) ~~Are you talking about guts? I don't know anything about those. I was talking about the language.~~	[reply] [d/l] [select]
Re^6: Splitting array into two with a regex by merlyn (Sage) on Nov 08, 2005 at 19:49 UTC
You're just looking at it sideways. {grin} The method needs to return an arrayref, which is then dereferenced by the @, and can thus be used in an lvalue context. `my $rec = bless {}; # main is the package my @sideeffected = qw(a b c); sub vals { return \@sideeffected } @{$rec->vals()} = qw(d e f); print "$_\n" for @sideeffected;` [download] That prints `d\ne\nf\n`. Maybe you thought I was talking about the inner part? I was talking about the whole string of text from the "@" to the "}". -- Randal L. Schwartz, Perl hacker Be sure to read my standard disclaimer if this is a reply.	[reply] [d/l] [select]
Re^7: Splitting array into two with a regex by ikegami (Patriarch) on Nov 08, 2005 at 19:52 UTC
ah yes! My eyes must have been crossed ;)	[reply]
Re^6: Splitting array into two with a regex by dragonchild (Archbishop) on Nov 08, 2005 at 20:00 UTC
I use that structure in Tree so that the basic methods (add_child(), for instance) can modify the children attribute without knowing how the children attribute is set up. All that matters is that children() returns an arrayref that guarantees it will be modifying the children (however the subclass set them up). So, there's a lot of `splice @{$self->children}, $idx, 0, $new_node;` stuff going on. My criteria for good software: Does it work? Can someone else come in, make a change, and be reasonably certain no bugs were introduced?	[reply] [d/l]