On Wed, 8 Oct 2003, Oleg Prokhorov wrote:
Change-log: fix wine code depended on
That's cool, but we need to somehow manage this. There are almost 300 occurences of memory reallocation, and we need to somehow keep track of what was reviwed/fixed etc., otherwise we risk missing quite a few...
We should start with a comprehensive list of things that need fixing...
Hello Dimitrie,
Thursday, October 9, 2003, 12:09:31 AM, you wrote:
DOP> On Wed, 8 Oct 2003, Oleg Prokhorov wrote:
Change-log: fix wine code depended on
DOP> That's cool, but we need to somehow manage this. That's a "testing" patch, if it gets committed I'll continue work on this :).
Dimitrie O. Paun wrote:
On Wed, 8 Oct 2003, Oleg Prokhorov wrote:
Change-log: fix wine code depended on
That's cool, but we need to somehow manage this. There are almost 300 occurences of memory reallocation, and we need to somehow keep track of what was reviwed/fixed etc., otherwise we risk missing quite a few...
We should start with a comprehensive list of things that need fixing...
Maybe we can add a new inline function which likes inline void *HeapReAllocEx(..., lpMemory, ...) { if (lpMemory)... else ... } then #define HeapReAlloc HeapReAllocEx in a proper header file.
-- Dimi.
"Jerry Jenkins" Jerry_J_Jenkins@hotmail.com wrote:
Maybe we can add a new inline function which likes inline void *HeapReAllocEx(..., lpMemory, ...) { if (lpMemory)... else ... } then #define HeapReAlloc HeapReAllocEx in a proper header file.
No, that will confuse people even more, and will abuse an exported API by a not appropriate functionality, which without looking at the headers will be very hard to identify.
-
Dimitrie O. Paun -
Dmitry Timoshkov -
Jerry Jenkins -
Oleg Prokhorov