Re: Are _T() and TEXT() macros equivalent?
David Ching wrote:
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.
Why do you say C++/CLI is a difficult language? There are some complicated
things in there but you do not have to use them for every day programming.
The main reason C++ is in demise is because Microsoft gave up on using it to
develop .NET programs from scratch, leaving them the only place to go is to
use it to extend existing native C++ programs with .NET features. This is a
worthy goal, but it makes C++/CLI used only in legacy situations. Of
course, people do still start new C++ projects, so I guess these would
benefit as well, although the number of people doing this is vastly
decreasing.
I think C++/CLI is a difficult language because it contains two entirely
different object models, and two entirely different libraries.
As I see it, C++ is trying to do three things at Microsoft:
1. Pure native apps (not the future?)
2. Adding .NET features to native programs (legacy apps only?)
3. Pure .NET development (will lose out to C# ?)
Failure to improve in either area 1 or 3 will drive people to C#, and it
is not so obvious where to put the effort. I say focus on 1, because
that is where almost all the current VC++ users are.
--
David Wilkinson
Visual C++ MVP