GObject in GC implementation Plan

[Josh Sled]

On Thu, 2007-03-22 at 10:39 -0400, Chris Shoemaker wrote:
> I think his point is that you can convert the engine objects to
> GObjects, using the g_object_new() and g_object_unref() in place of
> the current allocation/deallocation functions, but without actually
> tracking references between objects.
[...]
> the objects are all GObjects.  Conceptually, it's as if the "Engine"
> maintains a single reference on all engine objects.  There will only
> be the one reference added by the g_object_new(), and then unrefed at
> the end of the object's lifetime.  No calls to g_object_ref().

Yes, that is what I meant exactly.
Sorry I didn't make it as clear as this.

-- 
...jsled
http://asynchronous.org/ - a=jsled;b=asynchronous.org; echo ${a}@${b}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.gnucash.org/pipermail/gnucash-devel/attachments/20070322/debf694e/attachment-0001.bin