Hello!
        (sorry for my poor english first)
        I took a glance at the src of gobject. It's seemed that the gobject
doesn't have a "copy-on-write" function which QT's share class has.
(http://doc.trolltech.com/4.0/shclass.html)

        If u want to create thousands of GObject and don't modified them at
once, I suggest u use some methods which can achieve "copy-on-write" in
GObject ( I don't know how to do :( ).

btw: Why don't the developers of GObject add copy-on-write function to
GOject ?  Does the GObject really need copy-on-write ?
 

 2005-03-05 14:38 -0300,Fabrício Barros Cabral :
> Hi people!
> 
> I'm thinking develop an application using the GObject library, but I
> have a dilemma: use or not use the GObject library. This application is
> object-oriented but will be able to create-use-destroy a lot of objects
> (10.000 or more) during the execution of this application.
> 
> Thus, my question is: I should or I shouldn't use the GObject to make my
> objects? What is the impact of the overhead due using it?
> 
> 
> Best Regards,
> 
> --fx
-- 
Regards 
Falls Huang

_______________________________________________
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list

Reply via email to