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

[Ionutz Borcoman <borco borco-ei eng hokudai ac jp>]

Havoc Pennington wrote:
> 
> It keeps a pool of memory for different data types, such as linked list
> nodes. If you free a linked list node it goes back into the pool. This
> avoids calling malloc() and free() all the time; malloc() and free() are
> relatively slow functions to use.
> 
> I'm sure the glib guys are taking patches. :-)

Give me one reason to believe you that that memory is not leaking. How
are the guys from glib checking they don't have leaks ? I agree that I'm
not an expert, so please teach me how to do the stuff in the right way ?

Otherwise, all of these are just nice words and nothing more :-(

TIA (at least for the nice words :-)

Ionutz