I'd like to request support for _UNICODE / UNICODE
builds (for my Visual Studio 2005 code)
I DID read the post about this being too much work
(i.e. more testing), but I'm going to submit this
anyway, in hopes it gets done at some point.
Perhaps a good starting point to get this done would be
to use a single typedef / #define section to define an
alias to be used within the rest of the TinyXML
functions. i.e.
#ifdef _UNICODE
typedef const wchar_t* PC_TINY_STR
const std::wstring& STL_TINY_STR
#else
typedef const char* PC_TINY_STR
const std::string& STL_TINY_STR
#endif
This:
1) wouldn't change any of the existing code (in terms
of extra complexity, or making the project "un-tiny")
2) could be moved in a little at a time.
I realize this is not all that has to be done for
UTF-16 support, but it would make the rest of the
changes easier.
My two cents...
Warren
Logged In: NO
I second this request.
I don't see anyone using this library in a comercial app until
UNICODE support is available.
Logged In: YES
user_id=1207092
Please refer to my post in the patch section:
[ 1256162 ] using TinyXML with _UNICODE defined and
MFC/ATL CString
for the code I wrote for this issue.
Warren