Re: g_intern_static_string() for type names as small optimization

2008-01-16 Thread Behdad Esfahbod
On Wed, 2008-01-16 at 12:43 -0500, Matthias Clasen wrote: > > The thing is that GObject interns the type name anyway. But, as you > say, > it cannot assume that the string is static and thus calls > g_intern_string(), > causing it to be copied. By interning it using > g_intern_static_string() befo

Re: g_intern_static_string() for type names as small optimization

2008-01-16 Thread Andrew W. Nosenko
On Jan 16, 2008 7:43 PM, Matthias Clasen <[EMAIL PROTECTED]> wrote: > On Jan 16, 2008 11:24 AM, Andrew W. Nosenko <[EMAIL PROTECTED]> wrote: > > > > > I'm asking not about general benefits of an intern strings or GQuarks > > (which are backend of Glib's intern strings), but about benefits, which >

Re: g_intern_static_string() for type names as small optimization

2008-01-16 Thread Matthias Clasen
On Jan 16, 2008 11:24 AM, Andrew W. Nosenko <[EMAIL PROTECTED]> wrote: > > I'm asking not about general benefits of an intern strings or GQuarks > (which are backend of Glib's intern strings), but about benefits, which > expected by GTK/Glib developers, for constructs like (please, pay > attention

Re: g_intern_static_string() for type names as small optimization

2008-01-16 Thread Andrew W. Nosenko
On Jan 16, 2008 5:06 PM, Ross Burton <[EMAIL PROTECTED]> wrote: > On Wed, 2008-01-16 at 16:53 +0200, Andrew W. Nosenko wrote: > > Matthias (or anyone else), could you explain, what this "small > > optimization" optimizes (what use-cases, on what way, etc), why and > > how big win/profit gives? > >

Re: g_intern_static_string() for type names as small optimization

2008-01-16 Thread Emmanuele Bassi
On Wed, 2008-01-16 at 16:53 +0200, Andrew W. Nosenko wrote: > Cite from > http://mail.gnome.org/archives/gtk-devel-list/2007-April/msg00216.html > > "Matthias Clasen" wrote: > : On 4/27/07, Damon Chaplin wrote: > : : Why do the *_type_register_static() functions use > : : g_intern_static_stri

Re: g_intern_static_string() for type names as small optimization

2008-01-16 Thread Ross Burton
On Wed, 2008-01-16 at 16:53 +0200, Andrew W. Nosenko wrote: > Matthias (or anyone else), could you explain, what this "small > optimization" optimizes (what use-cases, on what way, etc), why and > how big win/profit gives? As the documentation says: "g_intern_static_string() does not copy the str

weakref semantics

2008-01-16 Thread jcupitt
I noticed the weakref introduction says that notifies can be called many times: http://library.gnome.org/devel/gobject/unstable/gobject-memory.html#gobject-memory-weakref ... which is invoked when the object runs its dispose method. As such, each weak ref can be invoked more than once upon

g_intern_static_string() for type names as small optimization

2008-01-16 Thread Andrew W. Nosenko
Cite from http://mail.gnome.org/archives/gtk-devel-list/2007-April/msg00216.html "Matthias Clasen" wrote: : On 4/27/07, Damon Chaplin wrote: : : Why do the *_type_register_static() functions use : : g_intern_static_string() for the type name? : : It is just a small optimization. Apps are free

Re: Nautilus+GIO vs GnomeApps+GNOMEVFS (aka: the clash on trash)

2008-01-16 Thread Alexander Larsson
On Tue, 2008-01-15 at 20:08 +0100, Mikael Hermansson wrote: > IMHO > > ALL desktops like KDE/GNOME and others MUST agree too KILL ~/.trash > totally and NOT support the old in GIO for example. instead we should > use .local/share/trash (if this is the freedesktop standard?. KDE4 uses the new t

Re: GIcon thoughts

2008-01-16 Thread Alexander Larsson
On Tue, 2008-01-15 at 21:59 -0500, Matthias Clasen wrote: > I have committed the stream i/o api in gdk-pixbuf now, after adding > GCancellable arguments > and removing the closing of the streams, since that seemed pretty > uncontroversial. > > Here are new versions of the resurrect-pixbuf and ico