[wx-dev] Re: #9672: wx 2.9 Ansi/Unicode Combi-wxString breaks compatibility with std::[w]string and introduces subtle errors

[Hajo Kirchhoff]

Hi Vadim,

>  If you mean whether we can assume that no existing code relies on wxString
> being implicitly convertible to both char* and wchar_t* then you're
> correct.

okay, great.

What other design ideas have you discussed besides the current one? I 
would like to do a bit of reading to catch up with your development.

I think I may have an idea that would meet all your requirements (one 
build, utf8, allow wxString("foo") for beginners, free ansi->unicode) 
and improve stl compatibility, backwards compatibility and also improve 
the current c_str() situation. It essentially uses two different string 
typedefs, one used by the wxWidgets library and one by wxWidgets 
applications.

But I don't want to post it in full length and waste time experimenting 
with it, if you have discussed it already and found problems which I am 
yet unaware of.

If I suggested a different solution to the wxString implementation, 
would it be welcome in principle? Or is the new wxString implementation 
already decided on with no changing back?

Best regards

Hajo