> On Mon, 04 Jan 2010, Bisz István wrote:
>> OK. Maybe I was too happy to see this message, sorry.
>
> Ups. I've just seen that it was not always shown but only
> when //INFO were used so it's fine for me. I only suggest
> to replace:
> hb_snprintf( buffer, sizeof( buffer ),
> HB_I_("Memory allocated but not released: none") );
> hb_conOutErr( buffer, 0 );
> with simple:
> hb_conOutErr( HB_I_("Memory allocated but not released: none"), 0 );
This is fine.
There is a bigger problem though behind this whole topic.
We're lured into the impression that HBQT doesn't leak memory.
I say this because HBQT in dynamic mode doesn't seem to be
using our memory allocation functions at all, so nothing is
tracked, which means we're getting a constant zero leak
whatever is happening inside HBQT.
Do you have any suggestions to how to force C++ to use our
own memory allocation function, or where to look for a solution?
Brgds,
Viktor
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
