Re: Are _T() and TEXT() macros equivalent?
David Ching wrote:
What's missing is CStringUtf8, in addition to CStringA and CStringW. This
would do what you want, but it could still be initiliazed with either a
LPCSTRor a LPWSTR.
Maybe, but actually the level of understanding of MBCS in CStringA is
extremely limited. For example, as we have discussed before, GetLength()
does not return the number of Unicode code points, or the the number of
glyphs, but rather the number of char's. Ironically, the main reason
CStringA needs to understand the code page is so it can be initialized
with a wide string :).
When I see the rate of features being added to C#, features being taken from
the best of the dynamic languages, and compare it to the "any year now" of
C++, there's simply no comparison. C++ just can't keep up.
I think you are really talking .NET versus MFC here, not C# versus C++.
Surely most features of .NET are available in C++/CLI?
[I could be wrong here; I know very little about C# and .NET. I do know
that LINQ will not be available in C++/CLI, perhaps because it uses
partial classes.]
I have to say that I am afraid that C++/CLI, rather than being the
savior of C++ within Microsoft, could accelerate its demise. Firstly
because it reinforces C++'s reputation as a difficult language (C++/CLI
really is a difficult language...). And secondly because trying (with
only partial success) to keep up with .NET diverts resources from native
code support.
--
David Wilkinson
Visual C++ MVP