GObjectification status

[Derek Atkins]

Daniel,

What "GObject code conventions" are these?  And how did I
not follow them?  Each object that I gobjectified has a
{qof,gnc}_<object>_{init,init_class,dispose,finalize} API
that we can (eventually) use.

Note that I don't think we'll EVER migrate from xallMallocFoo()
to using g_object_new() directly, so this is okay.  Eventually,
however, we WILL want to migrate to using g_object_unref()...
BUT that's still a ways off, only once migrate over to the
dispose() and finalize() methods.

Thanks,

-derek

"Daniel Espinosa" <esodan at gmail.com> writes:

> Please Derek, try to follow the GObject code conventions to be more
> clear about your work, and please see my e-mail get coments.
>
> 2007/4/4, Derek Atkins <warlord at mit.edu>:
>> After about 6 hours of work over the last few days I've got
>> all the qofinstance-derived data objects using gobject
>> initialization and deletion.  They all have hooks for init(),
>> dispose(), and finalize() so we can slowly migrate each
>> object over to being FULLY gobject controlled..  then
>> we can add other features.
>>
>> Take a look at the gobject-engine-dev-warlord branch.  I'd
>> like to merge this back into trunk this weekend unless I
>> hear objections.
>>
>> Enjoy.

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available