Re: Memory leaks

[John Emmas <johne53 tiscali co uk>]

On 9 Feb 2011, at 23:41, Carlos Pereira wrote:

> > something), but aside from that it's a pure waste of CPU cycles.
> >   
> Dear Allin,
> I am sorry, I totally disagree.
>
> I can only see two cases. Either fixing these hundreds and hundreds of mem leaks is easy or difficult.
> In the first case, is just a question of plain laziness and bad programming practises. The second case is 
> much worse, it means the code is badly designed.

I think Allin's point is that even though I deleted the object in my example app, the gtk shared library code 
is still technically available to be used by some other part of my program (without needing to be 
re-initialized).  In my example, I just happened to not use it.

But to go back to some of the earlier suggestions, maybe it would be beneficial to have some kind of unload() 
/ finish() / cleanup() functionality that could be invoked by users who need it.  That's what seems to be 
missing at present.

John