Hello Florian,
Saturday, April 16, 2005, 11:32:07 AM, you wrote:
>> You can define types wchar_t etc. and set these to AnsiChar or WideChar,
>> as desired.
FK> the whole file handling stuff uses the "A-versions" so
FK> it would require to make here at least overloaded versions. More
FK> complica
DrDiettrich wrote:
> "Yury B." wrote:
>
>
>>Two RTLs should be for Win32, one compiled for ANSI/DBCS and the other for
>>UNICODE UCS-2 (WinNT), where a special type,
>>say TUniString is AnsiString in the first version and
>>UnicodeString in the second version.
>>What do you t
"Yury B." wrote:
> Two RTLs should be for Win32, one compiled for ANSI/DBCS and the other for
> UNICODE UCS-2 (WinNT), where a special type,
> say TUniString is AnsiString in the first version and
> UnicodeString in the second version.
> What do you think of it?
IMO there exis
Hello fpc-devel,
If there were full unicode support (TCHAR analogue) the life under Win32
would be simpler $)
Two RTLs should be for Win32, one compiled for ANSI/DBCS and the other for
UNICODE UCS-2 (WinNT), where a special type,
say TUniString is AnsiString in the first version a
