Hi, I'm sitting here thinking about cross language calls and what I don't see anywhere is a prohibition that stops a context from popping a handler or action or whatever that it didn't place there.
Is there an intent to prohibit or restrict this kind of behaviour? It also seems to me that with coroutines and threads you might have diverging contexts with different active exceptions and actions. So is a stack the correct model for this or are we talking a hierarchical chain of contexts each with a stack. Sort of like the user stack I guess. Cheers, Steve Gunnell On Sat, 2006-01-07 at 20:36 -0500, Bob Rogers wrote: > This is an attempt to summarize my thinking about the instruction > interface to dynamic binding and its interaction with the other > dynamically-scoped bits of Parrot. I am hoping to get feedback before > diving further into the implementation details. > > Please let me know what you think. TIA, > > -- Bob Rogers > http://rgrjr.dyndns.org/
