What's the future of wxT() and _T()?

[Anders Larsen]

On Sat, 01 Dec 2007 12:47:01 +0100, Vadim Zeitlin wrote:

> 0. Don't change anything, let wxT() and _T() always generate wide strings.
> 1. Make wxT() do nothing but keep _T() as it is now
> 2. Make wxT() do nothing in UTF-8 builds, keep it as is under Windows
> 3. Make both wxT() and _T() do the same thing as wxSTRING_TEXT does
> 4. Make both wxT() and _T() do nothing

5. Remove wxT() and _T() completely (don't touch _T() if it's defined
   externally to wx)

I really don't know what I prefer - my first thought was that we would
need to change the macros in such a was as to preserve compatibility
with 2.8 - but OTOH breaking backwards compatibility is exactly what
a once-in-a-decade major release is for.

Cheers
Anders