Re: What's wrong with Common Lisp's lambda ?
- From: Duane Rettig <duane@xxxxxxxxx>
- Date: Thu, 28 Sep 2006 10:03:01 -0700
Barry Margolin <barmar@xxxxxxxxxxxx> writes:
In article <o0ven89fqi.fsf@xxxxxxxxx>, Duane Rettig <duane@xxxxxxxxx>
wrote:
Looks like a CPS issue to me, not a lambda issue (at least directly).
Since CL doesn't have continuations, I'm not sure there's really much of
a distinction. Lambda is the only way to make a closure, and the point
is that closures can't be used to re-enter a control context that has
been exited.
Yes, of course. My comment is directed toward the possible
interpretation of a statement like "something is wrong with CL lambda"
as being something revelationary; instead it falls under the subset of
things not specified by CL because CL doesn't specify continuations/CPS.
--
Duane Rettig duane@xxxxxxxxx Franz Inc. http://www.franz.com/
555 12th St., Suite 1450 http://www.555citycenter.com/
Oakland, Ca. 94607 Phone: (510) 452-2000; Fax: (510) 452-0182
.
- References:
- What's wrong with Common Lisp's lambda ?
- From: Karol Skocik
- Re: What's wrong with Common Lisp's lambda ?
- From: Barry Margolin
- Re: What's wrong with Common Lisp's lambda ?
- From: Duane Rettig
- Re: What's wrong with Common Lisp's lambda ?
- From: Barry Margolin
- What's wrong with Common Lisp's lambda ?
- Prev by Date: Re: What's wrong with Common Lisp's lambda ?
- Next by Date: Re: (read-from-string "#.(values) 42")
- Previous by thread: Re: What's wrong with Common Lisp's lambda ?
- Next by thread: ECL misbehavior when loading an ASD file
- Index(es):
Relevant Pages
|