Re: Are _T() and TEXT() macros equivalent?
- From: "David Ching" <dc@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 08 Apr 2007 19:21:29 GMT
"Mihai N." <nmihai_year_2000@xxxxxxxxx> wrote in message
news:Xns990D13E9961E8MihaiN@xxxxxxxxxxxxxxxx
Like for instance Unicode. C++/MFC has to deal with it.
The Delphi programmers need not, because Delphi has no clue about it :-)
Yeah, I'm no fan of Delphi either, but neither it is simply a "learning
tool" as some here have said. But my point is both Delphi and .NET don't
have to deal with this _T() nonsense. OK, Delphi doesn't support Unicode
period, and .NET it is understood (so you don't have to specify it). But
awhile ago I asked how come Microsoft didn't make a switch or some #define
or whatever that made default literal strings be Unicode without any
adornments. My point is that to satisfy some 3rd party standard, C++ is
more complicated than necessary...
Ok, joking aside, we have to understand that the SDK had to jump thru all
kind of hoops for backward compatibility. Just read Raimond Chen's blog
to get a feeling of that.
.... and having to refer everyone to the history of it all just makes it more
maddening.
I was many times tempted to say that this or that is crap, but thinking
of it, it's history, or reading that blog, made me realize that some
of the things have good reasons. Yes, it can be ugly, and look like crap,
but this is the price when you get an old OS and old API, and try to
get it working without breaking it to much.
Truthfully, your nugget that said define both UNICODE and _UNICODE should be
easy enough, but I think that .NET has raised the bar in terms of simplicity
and straightforwardness, and that is going to be the new standard by which
C++ is judged by, and my IMHO, it isn't doing so great right now, and the
attitude of explaining the situation away by referring to history isn't
going to help.
.NET is new, does not have all that baggage. But also because it is new
there is a lot of stuff that cannot do. So one has to go to interop
more often than one would like.
Yes, C++/CLI to the rescue.
-- David
.
- Follow-Ups:
- Re: Are _T() and TEXT() macros equivalent?
- From: Tom Serface
- Re: Are _T() and TEXT() macros equivalent?
- From: Joseph M . Newcomer
- Re: Are _T() and TEXT() macros equivalent?
- From: Mihai N.
- Re: Are _T() and TEXT() macros equivalent?
- References:
- Are _T() and TEXT() macros equivalent?
- From: Martin
- Re: Are _T() and TEXT() macros equivalent?
- From: Mihai N.
- Re: Are _T() and TEXT() macros equivalent?
- From: David Ching
- Re: Are _T() and TEXT() macros equivalent?
- From: MrAsm
- Re: Are _T() and TEXT() macros equivalent?
- From: David Ching
- Re: Are _T() and TEXT() macros equivalent?
- From: Mihai N.
- Re: Are _T() and TEXT() macros equivalent?
- From: David Ching
- Re: Are _T() and TEXT() macros equivalent?
- From: Mihai N.
- Are _T() and TEXT() macros equivalent?
- Prev by Date: Re: How many bytes per Italian character?
- Next by Date: Re: How many bytes per Italian character?
- Previous by thread: Re: Are _T() and TEXT() macros equivalent?
- Next by thread: Re: Are _T() and TEXT() macros equivalent?
- Index(es):
Relevant Pages
|
