Subj : Re: Problems with garbage collection and read-only properties.
To   : netscape.public.mozilla.jseng
From : "Chris Nuernberger" <chrisDOTnuernbergerATanark.com>
Date : Thu Nov 20 2003 03:16 pm

> The trade-off is simple: if you need to define your own private data
> (JS_SetPrivate, etc.), and especially if that private data struct is
> useful in your native (C or C++) code in its own right, then you
> probably want to use JSPROP_SHARED and manage the value storage
> yourself, in the private data, with your own JSClass.mark.  If you don't
> have per-object private data, or don't need to store the tinyid'd
> properties values there, you may as well use reserved slots.

That explains everything perfectly :).  Thanks a lot, using JSPROP_SHARED
and overriding JSClass.mark really will make the code cleaner and finally
work correct!!  (before we were just rooting everything to avoid the
problem, but now the time has come to solve it).

Chris

.