Thank you so much for your reply! I really appreciate it. Although I remember reading about this issue at some point in the past, I have used std::wstring under MingW-gcc for quite some time now with no problems. If it were really 100% incompatible I would wish it would give a compilation error! I wonder why it crashes under the 'ireplace' algorithms but not the 'replace' ones -- especially since I remain strictly within Unicode Plane 0 (basic 2-byte characters in UTF-16/UCS-2 which fit in a single wchar_t on Windows). In any event, if you have any further insight here I would be interested to hear it, but I suppose I will just have to change compilers. Thanks again! Pavol Droba wrote:
Hi,
On Tue, Jan 19, 2010 at 06:34:48PM -0500, Doug Swanson wrote:
I apologize in advance if this is an inappropriate place to post this question. I posted it to the boost-users list half a week ago and got no replies, so I am trying here instead.
I'm sorry I missed that.
The following code compiles and runs without error under g++ in Windows, GCC 3.4.2 (MingW):
<snip>
Does this indicate a problem with gcc (MingW) unicode support? Is there an easy way to circumvent it?
Thank you very much for any suggestions!
As far as I know, that answer is quite simple. Unless something have changed recently, mingw does not support unicode strings. I would suggest to swith to non-mingw version of gcc.
Best Regards. Pavol
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost