From: E. Gladyshev (egladysh_at_[hidden])
Date: 2002-03-26 17:05:35
> That's fine - client allocates/client frees. The
> reverse is fine too: DLL allocates/DLL frees. The
> problematic cases
> are Client allocates/DLL frees, and DLL
> allocates/Client frees.
I agree you better avoid the Client allocates/DLL
frees, and DLL allocates/Client frees desings.
It is a time bomb as you put it.
I think that one more or less safe way to do it
is to have one global memory management module
and always call it when dealing with memory
stuff. However you have to be careful
even in this case.
Do You Yahoo!?
Yahoo! Movies - coverage of the 74th Academy Awards®
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk