On Sun, 23 Jan 2005 10:33:38 +0100, Michael Stefaniuc wrote:
I thought more of checking the return value of HeapAlloc/HeapRealloc to make sure it's not NULL. This would be easy to do. What you proposed is too complicated.
Well, what happens if it is NULL? You can print an error and then return ... but then the code looks OOM safe even though it's actually not.
I guess that's similar to my thoughts on the Interlocked changes before though, it makes code that isn't thread safe look like it is.
thanks -mike