Re: Are _T() and TEXT() macros equivalent?
- From: "Tom Serface" <tom.nospam@xxxxxxxxxxxxx>
- Date: Thu, 5 Apr 2007 09:02:13 -0700
I always use _T(), but I'm guessing it wouldn't matter. You could easily define these macros in any port you did and there are so many other things that would cause you grief doing a port that this would likely not be top on your pain list.
Tom
"Martin" <martin-g@xxxxxxx> wrote in message news:1175788201.721580.207470@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Apr 5, 6:31 pm, "Martin" <marti...@xxxxxxx> wrote:Hello everybody!
I'd like to find out once and for all: can I always use _T() in place
of TEXT() and vice versa? If yes, why has _T() been added into
tchar.h? Wasn't TEXT() enough for us?
Thanks in advance
Martin
Hmm, I think I found the reason for defining '_T()'. 'TEXT()' is a
Windows specific macro (it's defined in winnt.h), so _T() is more
portable, am I right, what do you think?
Thanks,
Martin
.
- References:
- Are _T() and TEXT() macros equivalent?
- From: Martin
- Re: Are _T() and TEXT() macros equivalent?
- From: Martin
- Are _T() and TEXT() macros equivalent?
- Prev by Date: Re: Change CStatic fonts
- Next by Date: Re: WTL vs MFC : Same question as Yesterday
- Previous by thread: Re: Are _T() and TEXT() macros equivalent?
- Next by thread: Re: Are _T() and TEXT() macros equivalent?
- Index(es):
Relevant Pages
|