From: Allison Randal <[EMAIL PROTECTED]>
Date: Sat, 22 Jul 2006 17:34:45 -0700
Bob Rogers wrote:
> Two weeks ago I started writing something I had been thinking about for
> a year now, tentatively called "Continuations, Coroutines, And All That:
> An informal introduction to cre
Bob Rogers wrote:
Two weeks ago I started writing something I had been thinking about for
a year now, tentatively called "Continuations, Coroutines, And All That:
An informal introduction to creating advanced control structures in
Parrot." It is still mostly an outline, though -- it's hard to w
From: Allison Randal <[EMAIL PROTECTED]>
Date: Fri, 21 Jul 2006 00:24:13 -0700
chromatic wrote:
> Here's what I don't understand. Why is there talk of a stack to keep
track of
> various flow control constructs? Doesn't a CPS system use a linked list
of
> continuations to h
chromatic wrote:
Here's what I don't understand. Why is there talk of a stack to keep track of
various flow control constructs? Doesn't a CPS system use a linked list of
continuations to handle normal flow control? If that works there, why not
another linked list of continuations to handle
On Friday 14 July 2006 16:07, Bob Rogers wrote:
> One way to ensure that a handler is not in scope
> when invoked (though possibly not the only way) is to keep the list of
> active handlers in a dynamic variable binding.
Here's what I don't understand. Why is there talk of a stack to keep track
On Sat, Jul 08, 2006 at 04:51:38PM -0700, Allison Randal wrote:
> Chip did a fantastic job on the Exceptions PDD. With a few refinements,
> I'm pronouncing it "ready to implement".
Excellent.
Mad properties to Allison for creating the first draft (updating is so much
easier than starting from
