Re: delete does not free memory with CString
- From: Hans-J. Ude <news@xxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 27 Mar 2009 20:02:31 +0100
"Giovanni Dicanio" <giovanniDOTdicanio@xxxxxxxxxxxxxxxxx> wrote:
The better CString implementation is only one of these improvements.
There are others like better STL implementation, or some useful compiler
switches like /GS (that helps against buffer overruns) and much more.
The newer IDEs are somewhat slower than VC6 one (and the lack of ClassWizard
is a negative point if you do MFC development), but there are useful
features in the newer IDEs as well, in particular I like debugger
visualizers a lot (they make the debugging experience much better).
Just to not discourage the OP because of the lack of ClassWizard.
ClassWizard's functionality is still there but it's spread all over
the place and some functions like creating a control variable became
awfully slow.
Hans
.
- Follow-Ups:
- Re: delete does not free memory with CString
- From: Tom Serface
- Re: delete does not free memory with CString
- From: Ian Semmel
- Re: delete does not free memory with CString
- References:
- delete does not free memory with CString
- From: Kai Sandner
- Re: delete does not free memory with CString
- From: Giovanni Dicanio
- Re: delete does not free memory with CString
- From: Kai Sandner
- Re: delete does not free memory with CString
- From: Giovanni Dicanio
- delete does not free memory with CString
- Prev by Date: MFC Wizard
- Next by Date: Re: How to write vector<CString> to a text file?
- Previous by thread: Re: delete does not free memory with CString
- Next by thread: Re: delete does not free memory with CString
- Index(es):
Relevant Pages
|