[fpc-devel] Re: WinCE port patches

[Alexey Barkovoy]

>> How do MS compilers handle code written for both Ansi and Unicode
>> environments, and the related data types? How are string arguments (out)
>> handled in Windows API's?
>> Is this Microsoft way a good model for other platforms?
> 
> MS provides types for strngs/characters which are become differ if UNICODE 
> is defined or not.
> For example LPCTSTR is an LPCWSTR if UNICODE is defined, an LPCTSTR 
> otherwise.
> Therefore UNICODE define can easily convert MS RTL to unicode and 
> non-unicode versions.

And for Borland plan always was:

{$IFDEF UNICODE}
  String = WideString;
  Char = WideChar;
{$ELSE}  
  String = AnsiString;
  Char = AnsiChar;
{$END}

but seems it will not be realized for some or other reasons.