Bob Rogers wrote: > > There's no way to get full Continuations working around such C code > barriers, > except by *not* entering secondary runloops at all for these cases[1]. > This > could be achieved by (optionally) returning a new PC for all vtable/MMD > functions that is, by changing the internal (C) calling conventions of all > the PMC code. > > I see a solution for simpler cases, that might even work for custom sort > functions, though it's certainly not painless. Here's what I would like > to do for calling actions:
Bob, could you briefly write up the problem and proposed solution as a [PDD] ticket for the extending, embedding, and external C API PDDs (10-12, and possibly 2 and 23)? How we handle exceptions and control-flow across C/Parrot boundaries is an important question, and I want to make sure we address it. Thanks, Allison
