An another way is to use the Placement New/Delete mechanism on the previously allocated memory. Is a complete new area, with a lot of experimenting /testing issues.
-----Original Message----- From: harbour-boun...@harbour-project.org [mailto:harbour-boun...@harbour-project.org] On Behalf Of Bisz István Sent: 2010. január 3. 1:00 To: 'Harbour Project Main Developer List.' Subject: RE: [Harbour] SF.net SVN: harbour-project:[13444] trunk/harbour >What is the way to force our allocation functions to be >used by QT C++ new/delete operators? >Without this, any fm.c leak measurement is pointless >for QT subsystem, as our fmstat modules is just not used >at all by it. I can see hacks just for the static builds, but it is a hard way, in any case... _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
