To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=53572
------- Additional comments from [EMAIL PROTECTED] Sat Jan 14 23:40:46 -0800 2006 ------- Hi, Fellas, long time no see. I am trying to apply new policy to cope with wchar_t issue. As I wrote, defining sal_Unicode as unsigned short causes problems in MS- Windows specific modules. To minimize and limit the scope of the patches, I am trying to hack WINAPI headers. As wchar_t exactly has unsigned short characteristics (but not the same type), C calls are OK. C++ call may have problems, but WINAPI with C++ call is very limited and not used in OOo. Moreover, if the calling convention is C++, the API is not usable from MinGW because the name mangling is quite different. However, we have three additional problems. 1) C functions. Windows modules are freely using C functions exported from Microsoft VC runtime. MinGW provides the headers and they also have to be patched. 2) External (third party) projects Most of third party projects also use wchar_t if configured by normal configure script. They also need patches. Especially, uses of wchar_t in stlport have to be completely replaced by unsigned short because in MinGW stlport streams with non-standard type cannot be instantiated when dynamic linking is being used. 3) Literals Last but not least problem is string literals. Strings generated by L"" notation is of type "const wchar_t*" and not compatible with "const unsinged short*". Some MS-Windows specific modules are using macros for Unicode string literals and can be hacked by patching the header, but if the source code is not using macros, the only way is to patch the source itself. Maybe it is better to introduce a macro instead of hacking the header. I am afraid I have gone too far but the patch set seems to be the smallest with this way. I am now reorganizing, commenting and testing the patches with m150 and hopefully the patch set can be uploaded in a couple of weeks. Regards, tono (Takashi Ono) --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
