> And if lvalue access were made the only way of doing assignment of
> params in this context then a whole bunch of the code in param could
> be removed.
Maybe this is the confusion. I'm not saying subs should ONLY be lvalue.
I think they should be both rvalue and lvalue at the same time.
Automatically.
Did anybody look at this example?
@array = $r->func((split /:/, <PASSWD>)); # ok
@array = ($r->func) = split /:/, <PASSWD>; # same thing
-Nate
- RFC 107 (v1) lvalue subs should receive the rvalue as ... Perl6 RFC Librarian
- Re: RFC 107 (v1) lvalue subs should receive the r... Nathan Wiger
- Re: RFC 107 (v1) lvalue subs should receive the r... Damian Conway
- Re: RFC 107 (v1) lvalue subs should receive t... Jarkko Hietaniemi
- Re: RFC 107 (v1) lvalue subs should receive t... Nathan Wiger
- Re: RFC 107 (v1) lvalue subs should receive t... Damian Conway
- Re: RFC 107 (v1) lvalue subs should recei... Nathan Wiger
- Re: RFC 107 (v1) lvalue subs should r... Nathan Torkington
- Make lvalue subs the default (wa... Nathan Wiger
- Re: Make lvalue subs the def... Piers Cawley
- Re: Make lvalue subs the... Nathan Wiger
- Re: Make lvalue subs the... Andy Wardley
- Re: Make lvalue subs the def... Jonathan Scott Duff
- Re: Make lvalue subs the... Nathan Wiger
- Re: Make lvalue subs the... Jonathan Scott Duff
- Re: Make lvalue subs the... Nathan Wiger
- Re: Make lvalue subs the... Nathan Torkington
- Re: Make lvalue subs the... Nathan Wiger
- Re: Make lvalue subs the... James Mastros
- Re: Make lvalue subs the def... Nathan Torkington
- Re: Make lvalue subs the... Nathan Wiger
