Re: Are _T() and TEXT() macros equivalent?
David Ching wrote:
Since I hate STL notation, I guess we disagree with what makes a good
notation. As for strsafe not being the standard, I say, well, add it to the
bloody standard then if the standard is so important.
I don't like notations with underscores too much either. In fact I
really like the open-source strlcpy and strlcat, because they are simple
and have simple names. But they to not provide the variety of
safe-computing idioms that strcpy_s and friends or strsafe do.
Anyway, it seems that strcpy_s etc will be what makes it into the standard.
I agree with you that the standard can be infuriating. One of the most
annoying things is the refusal to allow opening of fstream (or even
wfstream) with a wide string argument on the grounds that "its meaning
would be ambiguous." I have never understood why it is more ambiguous
than using narrow strings, and on Windows it is clearly less so, because
there is only one wide string charactar set (UTF16) and many narrow
string ones. Not to mention that UTF16 is the native character set on
NT-based platforms. I think VC8 has added wide stream filename support
to fstream/wfstream, and this is a defiance of the standard that I
approve of :).
--
David Wilkinson
Visual C++ MVP