Re^6: Contexts and Perl 6

So, that would be a "no"? The concept of context flowing inward is deprecated.

Instead, constructs always do the same thing, which is to return an object that can exhibit different behavior in different contexts later. A simple example, which can be taken as an exemplar, is Nil which replaces "undef in item context or () in list context.".

Is that the plan?

—John

Comment on Re^6: Contexts and Perl 6 Select or Download Code

Replies are listed 'Best First'.
Re^7: Contexts and Perl 6 by TimToady (Parson) on May 20, 2009 at 16:54 UTC
You're asking for an answer that assumes we're using the same definition of "inward". The meaning of that term is unclear in the presence of continuations.	[reply]
Re^8: Contexts and Perl 6 by John M. Dlugosz (Monsignor) on May 20, 2009 at 17:53 UTC
"inward" as in overloading on return type. Where are continuations used in Perl 6? I don't see any language features that explicitly do that. As you said, resuming an exception is simply returning since the stack is not unwound. Closures are starting-off points that take their environment from the actual caller. No co-routine constructs or "live" label references, etc. Anyway, my question as it stands, is as has been mentioned on this thread and referenced posts. Or, is the whole conversation overlooking Something Important? —John	[reply]