On 10 July 2012 16:26, mschwartz <[email protected]> wrote: > I think we're in 100% agreement that finalization time is a poor time to > manage resource deallocation. This is the point of my suggestion that > there be some mechanism to register a destructor with the JS engine for the > object that is called when completely dereferenced. >
Well, again, how is the runtime supposed to find out, except by GC? That's how MakeWeak works, too. It is finalization. You can't do better, unless you buy into reference counting (with all its problems and overhead). > The ECMAScript 1.8.5 method I referenced is an example of how the language > (or environment) has evolved to address things lacking in previous versions > (such as the ability to protect properties from deletion). > OK, but I would argue that API design and evolution would be the trivial part of your proposal. /Andreas -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
