On 21.06.2005 23:12, Martin Fuchs wrote:
The pure existence of <include/tchar.h> in the Wine code base shows me, Wine is aimed to support TCHARs.
It may also just show that Wine wants to be compatible with existing sources that use <tchar.h>, it doesn't necessarily say anything about the internal use of it or whether new applications should employ it.
AFAIK TCHARs were devised quite a while ago to allow compilation of a single codebase for both ANSI (ie Win9x) and Unicode (ie WinNT) APIs. If you know you'll run on a platform that thoroughly supports Unicode, there's just no point in carrying around the TCHAR baggage. Make life for you and everyone else easier and give an example how to write a proper Unicode (and only Unicode) application.
-f.r.