Status of callcc

[Charles Oliver Nutter]

Lukas Stadler wrote:
> Hi!
> 
> I'm working on this for 1 1/2 months now (under Johns supervision). I've 
> implemented the deserialization part and I'm currently finishing an 
> alternative representation of the serialized stack that is more 
> accessible from the Java side. This should soon be finished and I'll 
> hopefully be able to submit a patch with this code within the next 1-2 
> weeks.
> I've written a few small applications, for example one that serializes 
> the stack to a file and resumes it later on, like a webserver that 
> hibernates an inactive session to a database.
> 
> performance: I haven't done any performance measurements yet. My code 
> hasn't evolved far enough (I'm only working on the openjdk project for 1 
> 1/2 months now, part time...) but there's a paper on a similar approach 
> to continuations in a JVM that also discusses performance: 
> http://lamp.epfl.ch/~dragos/files/ecoop-workshop.pdf
> 
> completeness: I'd say it's under development, and with the public API 
> comes the task of finding and dealing with all the VM invariants that 
> can be broken by this. And security, of course, is a big question too. 
> There's ongoing communication on these points on this mailing list, 
> under the subject "stack manipulation API"

Thanks very much for the update. I will track that thread and try to 
weigh in where I'm able. And I'll certainly be ready to play with it 
when you feel like it's in at least "usable enough" experimental state 
to start trying things out..

- Charlie