Juan Lang wrote: > On Dec 5, 2007 12:52 PM, Michael Stefaniuc <[EMAIL PROTECTED]> wrote: >> Checked with Kai and Dmitry and there is nothing special about >> SECUR32_ALLOC(). There are more direct usages of HeapAlloc() >> than of the macro so instead of replacing SECUR32_ALLOC() with >> heap_alloc() just remove it altogether. > > No prob. I introduced those macros some years ago before valgrind was > usable with wine, it made debugging memory leaks (via redefinition of > the macros with special leak-tracking ones) easier. Valgrind is > certainly better. I thought that was still the reason why those $dll_alloc() and now heap_alloc() wrappers are used. I mean the main reason cause we all know that the HeapAlloc() API just sucks.
bye michael -- Michael Stefaniuc Tel.: +49-711-96437-199 Sr. Network Engineer Fax.: +49-711-96437-111 -------------------------------------------------------------------- Reg. Adresse: Red Hat GmbH, Hauptstätter Strasse 58, 70178 Stuttgart Handelsregister: Amtsgericht Stuttgart HRB 153243 Geschäftsführer: Brendan Lane, Charlie Peters, Michael Cunningham, Werner Knoblich