Re: Cstring WriteString not working also write not working

From:

"David Ching" <dc@remove-this.dcsoft.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Wed, 28 Jan 2009 13:39:54 -0800

Message-ID:

<7FA2B63C-4922-4D5F-B6F9-1E9AED6EEEBD@microsoft.com>

"Giovanni Dicanio" <giovanniDOTdicanio@REMOVEMEgmail.com> wrote in message
news:OlbB%23TXgJHA.5844@TK2MSFTNGP05.phx.gbl...

CArray: 6427 ms
STL vector: 655 ms

With poor CArray resizing algorithm the process takes more than 6 seconds,
instead with STL vector you are below 1 second (about half a second).
STL vector is a clear winner!

Hi G, I've heard if you call CArray::SetSize() with a value exceeding the
maximum number of expected elements in the array, the resulting performance
will pretty much match the STL one. It would be interesting if you could
rerun your benchmark after calling CArray::SetSize(500000) to verify that.
STL doubles the size of the buffer every time it needs to resize, thus
having to do costly resizing much less often than MFC. With RAM in
abundance today, that is a good strategy, but back when MFC was written, it
would have seemed like an irresponsible waste of a scarce resource.

The thing is, even with having more time to develop, STL is still saddled
with a more cumbersome syntax and usage model than MFC. :-)

Thanks,
David