Re: Deprecate GdkGC?

2005-12-03 Thread Alexander Larsson
On Fri, 2005-12-02 at 09:43 +0100, milosz derezynski wrote: > Well, i volunteer for this. I have used cairo extensively for coding > bmpx and i'm going to get to a very good point in documenting at least > all the equivalents of gdk_draw_*() > > Federico: In which format should i write this, anyth

Re: landing g_slice_*() in glib

2005-12-03 Thread Tim Janik
On Fri, 2 Dec 2005, Paul LeoNerd Evans wrote: On Fri, 02 Dec 2005 09:44:04 +0100 Alexander Larsson <[EMAIL PROTECTED]> wrote: Also, are you making GType use g_slice for allocation of objects instead of memchunks (if n_preallocs is set)? And what of the allocators used by GString / GList / GS

g_slice_

2005-12-03 Thread Morten Welinder
I might be dense, but what exactly does g_slice_ buy us over plain, old malloc? * Don't say speed. That's a bogus argument because you cannot possibly have tested all mallocs. * Don't say overhead for the same reason. What do we pay? * We have probably killed tools like Purify that know abou

Re: g_slice_

2005-12-03 Thread Behdad Esfahbod
On Sat, 3 Dec 2005, Morten Welinder wrote: > I might be dense, but what exactly does g_slice_ buy us over > plain, old malloc? > > * Don't say speed. That's a bogus argument because you cannot > possibly have tested all mallocs. It's tested with the glibc implementation, and that buys us speed

Re: g_slice_

2005-12-03 Thread Dave Benson
On Sat, Dec 03, 2005 at 10:35:38PM -0500, Behdad Esfahbod wrote: > On Sat, 3 Dec 2005, Morten Welinder wrote: > > > I might be dense, but what exactly does g_slice_ buy us over > > plain, old malloc? > > > > * Don't say speed. That's a bogus argument because you cannot > > possibly have tested

Re: g_slice_

2005-12-03 Thread Behdad Esfahbod
On Sat, 3 Dec 2005, Dave Benson wrote: > i have two sort-of related questions: > - doesn't this belong in glibc? > - why isn't it implemented as g_mem_set_table(g_slice_allocator)? No, the difference is that for no-overhead allocation to be possible, g_slice implementation is using the fact t

Re: RFC: warnings on ignoring return value on some list operations

2005-12-03 Thread Matthias Clasen
On Thu, 2005-12-01 at 18:40 +0100, Alexander Larsson wrote: > On Thu, 2005-12-01 at 12:39 +0100, Tim Janik wrote: > > > and there were no strong objections after that. so it'd be nice if you > > provided > > a patch that covered all list functions. i think that can get commit > > approval > > ri