Talk:Microsoft Visual C++ Guide

From WxWiki

The "What is Unicode?" section at http://wxwidgets.org/manuals/stable/wx_unicode.html is technically not correct.

You have to distinguish between Unicode characters and Unicode encoding. You can encode a Unicode string using UTF-8, UTF-16 or UTF-32. The UTF-8 encoding uses a byte stream, but one Unicode character being represented possibly by multiple bytes. This means, an application can fully support Unicode but still using 8-bit strings. UTF-16 (as used by teh Unicode support of wxWidgets) uses a stream of 16-bit integers. But also here one Unicode character may be represented multiple bytes. ("Surrogates").

• If you feel this is really a problem in the official documentation, please either submit a bug on the bug tracker, or submit an actual patch to the documentation fixing this error. Your comment here won't help to resolve the problem. --Tierra 14:13, 2 March 2007 (PST)

[edit] wx_dll only for dynamic libraries

Will the project compiled with a solution file converted from wx_dll.dsw really just work properly for dynamic libraries? According to the documentation the only difference to wx.dsw is the added dependencies, so I see no reason why this could interfere with the build process for static libraries.

• You're right, it doesn't. You could use wx_dll.dsw for either static or dynamic libs without any issues, and maybe some point in the future, it will finally be narrowed down to just using wx.dsw with the dependency information, but the separation was needed in the past, and it doesn't hurt to be like this for now (except for those building dynamic libs that fail to read the documentation and try building it with wx.dsw, but that's their own fault since it's mentioned in multiple guides including this one and the official docs). It's possible that it also continues to be this way just because of the way that Bakefile generates the Visual C++ project files. --Tierra 14:55, 28 August 2007 (PDT)