Re: [gtk-list] Re: how can I trust glib when it has so many memleaks?

[Havoc Pennington <rhp zirx pair com>]

On Thu, 18 Mar 1999, Kevin Handy wrote:
> 
> I've split the program up into two, an the malloc/free is now faster
> for a single iteration. I also added code to allow changing the size
> multiplier to see if that made much difference between the two (it
> didn't). Also lost the malloc(0)'s
> 

You're missing the larger point Lars made, which is that g_malloc() is
totally irrelevant to this discussion, it's just a malloc() wrapper.
Read the source for GMemChunk and look at gslist.c for an example use.
g_malloc() is obviously going to be the same speed as malloc(), more or
less. A quick glance at gmem.c would make this obvious to you.

This is why I'm saying everyone should read the code before posting
further.

Havoc