> > closure serialization definitely works, I have tried round tripping > compiled and interpreted procedures with and without surrounding context > through serialize and deserialize and they are still functional after > reading them back in.
Excellent. > > Continuations should work, too, but it is non-trivial to construct a > continuation that doesn't close over all sorts of crazy stuff like the > input ports from which the interpreter reads library files etc. Fiddling > around with green threads to delimit the continuations and using the > facilities to inject "external dependencies" into the serialization > context of protobuf should do the job, though. Well, ports for example will never be fully serializable (with the exception of "standard" ports). Have you seen "suspensions"? https://wiki.call-cc.org/eggref/4/suspension They currently use "s11n" but "protobuf" would be the better mechanism. This might be the path for having a real "termite" for chicken ... cheers, felix _______________________________________________ Chicken-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-users
