On 21.06.2005 23:44:21 Frank Richter wrote:
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.
Sure, <tchar.h> is not designed to be used "internally" in Wine. But the point is, I would like to maintain Winefile such, that it isn't constraint to being used in Wine only. For example it is currently also present in ReactOS. The idea is to allow compiling it in ANSI mode for that cases, that don't provide or need Unicode. Win 9x systems don't provide Unicode functions. Embedded systems don't have available much memory resources, so they try to spare as much memory as possible. Currently there isn't yet a ReactOS port for such environments. But why not prepare for such a situation yet now?
Regards,
Martin