On Monday, September 2, 2002, at 11:35 AM, Sisyphus wrote: > > Only time I used 'malloc()' and 'free()' in an inline function I struck > problems if the function was called a number of times. I forget > just how big that 'number of times' was - and the amount of > memory involved might well have had a bearing. (It worked fine > if the function was called only once - which led me to believe > that 'free()' was not doing the job, and the memory was being > freed only when the app terminated.) > > Someone posted the recommendation that 'New()' and 'Safefree()' be used > instead, and I've been using them with no trouble.
You could be right - I wasn't sure whether New() and Safefree() would work properly with both -Dusemymalloc and without it. Is it safe in both situations? -Ken
