Re: Some details of function return captures

TSa (Thomas Sandlaß) thomas-at-sandlass.de |Perl 6| wrote: ... my $x = |$obj.foo(1,2); #4 to keep the ReturnCapture, and call it later either explicitly $x.resume(3); or implicitly $x = 3; Hope that helps, TSa. Interesting idea, as an alternative to get/set methods like

Re: Some details of function return captures

HaloO, On Saturday, 9. August 2008 01:32:35 John M. Dlugosz wrote: > TSa Thomas.Sandlass-at-barco.com |Perl 6| wrote: > > If such a ReturnCapture could also be > > preliminary of some kind, then lvalue subs could be lazily resumed when > > the rvalue comes in. > > Can you elaborate on that? I don

Re: Some details of function return captures

TSa Thomas.Sandlass-at-barco.com |Perl 6| wrote: If such a ReturnCapture could also be preliminary of some kind, then lvalue subs could be lazily resumed when the rvalue comes in. Can you elaborate on that? I don't follow. Also infix: needs a lazy item that is collapsed into Int, Num or Ra

Re: Some details of function return captures

HaloO John M. Dlugosz wrote: I was trying to figure out exactly how Captures manage to stay invisible even though functions return them, yet still let you use Capture objects when you want to. Please see my conclusions at . The Summary at the ver