[Python-ideas] A Continuations Compromise in Python

Gerald Britton gerald.britton at gmail.com
Wed May 6 15:38:29 CEST 2009


<sarcasm>
Perhaps we should implement "come from" and "go to" while we're at it.
 Oh, let's not leave out "alter" (for those of you old enough to have
used COBOL) as well!
</sarcasm>

On Tue, May 5, 2009 at 11:31 PM, Jim Jewett <jimjjewett at gmail.com> wrote:
> On 5/5/09, spir <denis.spir at free.fr> wrote:
>> Le Tue, 5 May 2009 07:29:22 -0500,
>> John Graham <john.a.graham at gmail.com> s'exprima ainsi:
>
>>> I had another proposal on the actual keyword front,
>>> "return from", which looks like it would kind of provide some symmetry
>>> to the 'return' and 'yield' constructs and also reads pretty
>>> intuitively, in my opinion.
>
>> Sounds good imo.
>> return --> the process does not go farther in the curent func
>> from   --> there a detour
>
> Starting with a clean slate, I would agree.
>
> In practice, "return from" may already have too strong an association
> with its use in lisp-like languages.  The real meaning here is closer
> to GOTO; I would expect a "return from" to pop several layers from the
> stack (rather that simply replacing the current one).
>
> -jJ
> _______________________________________________
> Python-ideas mailing list
> Python-ideas at python.org
> http://mail.python.org/mailman/listinfo/python-ideas
>



-- 
Gerald Britton



More information about the Python-ideas mailing list