Roumen Petrov <[EMAIL PROTECTED]> added the comment: I couldn't find in MSDN flags for Windows CE compilers similar to the GCC compiler that change representation of strings in C-code. The Microsoft recommend so called TCHAR technology that depend from UNICODE define I answer itself.
>From MSDN isn't so clear what is status of CE version 6.0 - R2?. The documentation of CE 5.0 looks complete, include details for compiler, migration guide. About wince_compatibility.h/c - it is just a part of the patch (PythonCE-2.5-20061219). If we look in the complete patch we see changes like GetLocaleInfo->GetLocaleInfoA(_localemodule.c) but windll.kernel32.GetProcAddress->cdll.coredll.GetProcAddressW (test_random_things.py). Another change (posixmodule.c) CRYPTACQUIRECONTEXTA->CRYPTACQUIRECONTEXT. So we see changes from xxx to xxxA, xxx to xxxW, xxxA to xxx (!). If this patch required for CE 5.0 ? If not why to change now for may upcoming 6.0 ? If the python switch to W functions then the issue will be resolved. Without general switch to W functions and to wide strings we need to convert every time from single chat to wide char. Is this acceptable in general ? (for the particular case yes - the method is called rarely). _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4075> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
