"Jonathan H.H. Bloedow" <jbloedow at real.com> wrote:

> This change is designed to allow the CHXBuffer to keep track of the size of 
> the allocation(s) that it has made so that if a buffer is resized down 
> below its actual allocation size, it can be resized back up to the original 
> allocation size without doing a completely unnecessary reallocation.
> 
> Please let me know if you see any problems with this implementation.

Would it make more sense to manage m_ulAllocLength in the Allocate(),
Reallocate() and Deallocate() methods?

Also...for whoever ends up messing with the binary dist libs, since this adds
a member to a public header file that could get used by both the dist libs and
the public source code...builds might break.  Does the code going into the
binary dist libs all deal with IHXBuffer?  Or does some of it deal with
CHXBuffer directly?

Scott

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe at common.helixcommunity.org
For additional commands, e-mail: dev-help at common.helixcommunity.org