On Thu, Aug 17, 2000 at 05:10:40PM -0400, Buddha Buck wrote: > SO what you are saying is that the proper execution of "$p->foo(@args) += > $val;" should be (equivalent to): > > 1. Evaluate $val and get an rvalue $rval. > 2. Evaluate $p->foo(@args) and get an lvalue $lfoo. The order of those two is debatable. How do you know what context to evaluate the RHS in ? > 3. Add $rval to the rvalue associated with $lfoo, to get $rbar. > 4. call $lfoo->operator=($rbar) to do the actual assignment. No. you perform normal assignment. If the lvalue return has = overloaded then it will be called. Graham.
- Re: RFC 118 (v1) lvalue subs: parameter... Chaim Frenkel
- Re: RFC 118 (v1) lvalue subs: parameter... Damian Conway
- Re: RFC 118 (v1) lvalue subs: parameter... Nathan Torkington
- Re: RFC 118 (v1) lvalue subs: parameter... Hildo Biersma
- Re: RFC 118 (v1) lvalue subs: parameter... Nathan Torkington
- Re: RFC 118 (v1) lvalue subs: parameters, explicit ... Buddha Buck
- Merge RFC's 107 and 118 (was Re: RFC 118 (v1) l... Nathan Wiger
- Re: RFC 118 (v1) lvalue subs: parameters, explicit assig... Damian Conway
- Re: RFC 118 (v1) lvalue subs: parameters, explicit ... Johan Vromans
- Re: RFC 118 (v1) lvalue subs: parameters, explicit ... Buddha Buck
- Re: RFC 118 (v1) lvalue subs: parameters, explicit ... Chaim Frenkel
- Re: RFC 118 (v1) lvalue subs: parameters, explicit ... Nathan Wiger
- Re: RFC 118 (v1) lvalue subs: parameters, expli... David L. Nicol
- Re: RFC 118 (v1) lvalue subs: parameters, explicit ... Damian Conway