If dFree() is just free() now, is there a good reason not to remove it?
On Fri, Nov 09, 2012 at 12:47:14AM +0000, corvid wrote:
If dFree() is just free() now, is there a good reason not to remove it?
Yes, it matches dNew & dNew0 (mnemonic). Also, it gets simpler to profile/debug memory allocation, by instrumenting those primitives. -- Cheers Jorge.-
Jorge wrote:
On Fri, Nov 09, 2012 at 12:47:14AM +0000, corvid wrote:
If dFree() is just free() now, is there a good reason not to remove it?
Yes, it matches dNew & dNew0 (mnemonic).
Also, it gets simpler to profile/debug memory allocation, by instrumenting those primitives.
How about #define dFree() as free(), then?
On Fri, Nov 09, 2012 at 05:18:45PM +0000, corvid wrote:
Jorge wrote:
On Fri, Nov 09, 2012 at 12:47:14AM +0000, corvid wrote:
If dFree() is just free() now, is there a good reason not to remove it?
Yes, it matches dNew & dNew0 (mnemonic).
Also, it gets simpler to profile/debug memory allocation, by instrumenting those primitives.
How about #define dFree() as free(), then?
Or #define free when you need to debug. Or use LD_PRELOAD.
participants (3)
-
corvid＠lavabit.com -
jcid＠dillo.org -
p37sitdu＠lavabit.com