Dan Sugalski <[EMAIL PROTECTED]> wrote:
> On Mon, 18 Aug 2003, Leopold Toetsch wrote:
>> Or coroutines shouldn't swap the control stack - I don't know.
> They should, sort of.
> Coroutines are a pain, but what they have to do is keep track of both the
> top *and* bottom of their saved stacks. Wh
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> On Mon, 18 Aug 2003, Leopold Toetsch wrote:
>> Or coroutines shouldn't swap the control stack - I don't know.
> They should, sort of.
> Coroutines are a pain, but what they have to do is keep track of both the
> top *and* bottom of their saved stacks. Wh
On Mon, 18 Aug 2003, Leopold Toetsch wrote:
> Or coroutines shouldn't swap the control stack - I don't know.
They should, sort of.
Coroutines are a pain, but what they have to do is keep track of both the
top *and* bottom of their saved stacks. When a coroutine with active state
is invoked, it n
Michal Wallace <[EMAIL PROTECTED]> wrote:
> It seems that exception handlers get tied to
> subroutines when they're created, not when
> they're actually used. For example:
> ## this works:
> try:
> f = make_function()
> f.die() # raise some error
> except:
> pa
It seems that exception handlers get tied to
subroutines when they're created, not when
they're actually used. For example:
## this works:
try:
f = make_function()
f.die() # raise some error
except:
pass
## this does not work:
f = make_function()
