Andreas Pflug wrote:

Didn't 10.3 supply wchar_t (in contrast to 10.2, which lacks it)?!?

I believe that it does, but since I don't have 10.3 yet, I can't say for sure. What I can say is that the error we're talking about has to do with the lack of Unicode support compiled into wxWindows on Mac OS X. Perhaps a --with-unicode might solve the problem?

ahp

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

Reply via email to