Hi,
Is there any particular reason we don't use HeapAlloc/HeapReAlloc in winetest?
The rest of our programs do, but winetest uses malloc and realloc.
Cheers,
Paul.
Paul Vriens [EMAIL PROTECTED] writes:
Is there any particular reason we don't use HeapAlloc/HeapReAlloc in
winetest? The rest of our programs do, but winetest uses malloc and
realloc.
I can't recall any. I'm more comfortable with the latter, since
winetest is the only Win32 application I've
Ferenc Wagner wrote:
Paul Vriens [EMAIL PROTECTED] writes:
Is there any particular reason we don't use HeapAlloc/HeapReAlloc in
winetest? The rest of our programs do, but winetest uses malloc and
realloc.
I can't recall any. I'm more comfortable with the latter, since
winetest is the only
Paul Vriens [EMAIL PROTECTED] writes:
Ferenc Wagner wrote:
Paul Vriens [EMAIL PROTECTED] writes:
Is there any particular reason we don't use HeapAlloc/HeapReAlloc in
winetest? The rest of our programs do, but winetest uses malloc and
realloc.
I can't recall any. I'm more comfortable with
Paul Vriens [EMAIL PROTECTED] wrote:
Is there any particular reason we don't use HeapAlloc/HeapReAlloc in winetest?
The rest of our programs do, but winetest uses malloc and realloc.
I recall that replacing malloc/realloc by HeapAlloc/HeapReAlloc has fixed
user32/tests/msg.c failures under
