Re: AfxMessageBox?

I think "easier to type" is appropriate so long as it still accomplishes the
task. For example, if you are sure you are never going to need a
non-unicode version (and why would you anyway) thne the _T() stuff seems
like overkill...

Tom

"Mihai N." <nmihai_year_2000@xxxxxxxxx> wrote in message
news:Xns987BD0AEBD301MihaiN@xxxxxxxxxxxxxxxx
"David Ching" <dc@xxxxxxxxxxxxxxxxxxxxxx> wrote in
news:AKj6h.7078$6t.4382@xxxxxxxxxxxxxxxxxxxxxxxxxx:

"Mark Randall" <markyr@xxxxxxxxxxxxxx> wrote in message
news:%238iBRi%23BHHA.4892@xxxxxxxxxxxxxxxxxxxxxxx
/me uses this thread to point out that _T( ) sucks and with the # of
platform extensions MS has you would think they could have put a single
character prefix in (like the L) that converted to unicode if relevant.

The _T( ) is just damned messy.


I concur 100%. If I know my code is always going to be compiled UNICODE,
I
just use L"" and be done with it, just because it is easier to type.

"Easier to type" is not an argument.
It is easier to not check for errors, not catch exceptions, not check
buffer
overruns.
If you have better arguments, I am willing to listen :-)


--
Mihai Nita [Microsoft MVP, Windows - SDK]
http://www.mihai-nita.net
------------------------------------------
Replace _year_ with _ to get the real email


.

Loading