|
Ok, this might seem a little stupid. Case scenario,
I’m using a lib that allows me to create a complex object which I wrap in
an abstract and pass to the handling Neko code. Problem is, this abstract
value requires cleanup (what abstract value doesn’t), so a close function
will need to be called at some point. If I, instead, specify that the abstract
value is cleaned up after using val_gc( my_abstract, close ), then does this
handle calling the close function for me on this abstract without my needing to
worry about calling it myself… ie, when the Neko code finishes executing? I guessI already know thiat this is so, but I’ve
only just staggered onto the val_gc function and can’t believe I didn’t
notice it far sooner. Lee |
-- Neko : One VM to run them all (http://nekovm.org)
