[wx-dev] Re[2]: What's the future of wxT() and _T()?
Vadim Zeitlin
vadim at wxwidgets.org
Sat Dec 1 07:10:45 PST 2007
On Sat, 1 Dec 2007 15:38:04 +0100 Vaclav Slavik <vslavik at fastmail.fm> wrote:
VS> Vadim Zeitlin wrote:
VS> > So maybe we could use wxSTR() or even wxS()?
VS>
VS> These are meaningless, but then, so is wxSTRING_TEXT, so I wouldn't
VS> mind wxS (I like it better than wxSTR because it's shorter). And we
VS> didn't backport wxSTRING_TEXT to 2.8 yet, although I thought we
VS> already did, so it's still OK to change it.
I think wxSTR is slightly more clear than wxS ("STR" meaning just
"string", not "wxString") but I agree that being shorter is an important
advantage for such an often used macro.
Is anybody against wxS()? AFAICS there is no existing code using wxS() nor
(not that we want to define it but just to avoid confusion) _S().
Thanks,
VZ
More information about the wx-dev
mailing list