Joe Wilson a écrit :
Any thoughts about adding precise garbage collection to Neko?
Or does the code implicitly assume precise GC throughout its design?
Neko is currently using the (consersavative) Boehm GC
(its author compare the approach with a precise gc
http://www.hpl.hp.com/personal/Hans_Boehm/gc/conservative.html)
The only problem I see with precise GC is that it requires a lot more
macro work when writing C primitives and you can easily introduce GC
bugs if you forget to register one of your stack values. OCaml is a good
example of this, and I wanted to keep Neko C API as much easy as possible.
Best,
Nicolas
--
Neko : One VM to run them all
(http://nekovm.org)
