Re: Why doesn't CMap have a copy constructor?

From:

"Tom Serface" <tom@nospam.camaswood.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Fri, 30 Jan 2009 13:05:24 -0800

Message-ID:

<172C7078-6597-4789-949D-2BDB68F9D23D@microsoft.com>

I figure if you're doing an MFC project why not use CString since it comes
for free. If not, then just calling the SDK functions for loading strings
is not so difficult. Of course, you miss out on the built in functionality
of the string table which is really nice. If someone is doing a desktop
application in C++ and has to do it for more than one language they can save
themselves a lot of grief by just starting with the MFC paradigm and making
it work.

Tom

"Giovanni Dicanio" <giovanniDOTdicanio@REMOVEMEgmail.com> wrote in message
news:e39FnUxgJHA.564@TK2MSFTNGP03.phx.gbl...

"Leo Violette" <nineballer@comcast.net> ha scritto nel messaggio
news:ub73fNwgJHA.1292@TK2MSFTNGP02.phx.gbl...

I agree with your point and meant no disrespect in offering a method to
iterate the keys of a container.

Leo: no problem! :)
I've never assumed any form of disrespect.

I think that's the primary reason why, given the choice between CString
and std::string, I'll always choose CString.

Yes, CString offers also useful methods for internationalization, loading
strings from resources, etc. such that I find it more convenient than the
std::string.

Giovanni