precise gc?

Any thoughts about adding precise garbage collection to
Neko?
Or does the code implicitly assume precise GC throughout its
design?


     
____________________________________________________________
________________________
Park yourself in front of a world of choices in alternative
vehicles. Visit the Yahoo! Auto Green Center.
http://autos.yah
oo.com/green_center/ 

-- 
Neko : One VM to run them all
(http://nekovm.org)

--- Joe Wilson <developiryahoo.com> wrote:
> Any thoughts about adding precise garbage collection to
Neko?
> Or does the code implicitly assume precise GC
throughout its design?

I meant to write:
Or does the code implicitly assume conservative GC
throughout its design?


     
____________________________________________________________
________________________
Luggage? GPS? Comic books? 
Check out fitting gifts for grads at Yahoo! Search
http://search.yahoo.com/search?fr=
oni_on_mail&p=graduation+gifts&cs=bz

-- 
Neko : One VM to run them all
(http://nekovm.org)

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/conse
rvative.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)