[fpc-devel] Unicode in the RTL (my ideas)

Ivanko B ivankob4mse2 at gmail.com
Tue Aug 21 08:10:31 CEST 2012

I obviously have lot of issues with the RTL suggestions being thrown
 around in the past. eg: I have heard lots about the RTL mostly likely
 being UTF-16 only, or being spilt into 3 versions AnsiString,
How about supporting in the RTL all versions of UCS-2 & UTF-16 (for
fast per-char access etc optimizations) and UTF-8 (for unlimited
number of alphabets) ? Though larger work but it will satisfy everyone
& won't break the existing toolkits.

2012/8/21, Hans-Peter Diettrich <DrDiettrich1 at aol.com>:
> Graeme Geldenhuys schrieb:
>>       UnicodeString = type AnsiString(CP_UTF16);
> AnsiStrings consist of bytes only, for good reasons (mostly
> performance). The Delphi developers wanted to implement what you
> suggest, but dropped that approach later again.
> String classes have the same performance problems, so that e.g. in .NET
> it's suggested to use functions instead of string operators. In Delphi
> and FPC compiler magic is used instead of classes.
>>    {$ELSE}
>>       // probably not strictly correct, but assuming *nix here. But
>> you get the idea
>>       UnicodeString = type AnsiString(CP_UTF8);
>>    {$ENDIF
>>    String = type UnicodeString;
>>    Char = type String[4];   // the maximum size of a Unicode codepoint
>> is 4 bytes
> A character type is somewhat useless, unless all strings are UTF-32
> (what's quite unlikely now). Instead substrings should be used, which
> can contain any number of bytes or characters.
> You also have to explain what String[4] means in an Unicode environment.
> The ShortString type does not have an encoding, and thus is deprecated
> in a Unicode environment.
> Q: Did you ever read about the new string implementation of FPC?
> Do you really want to reinvent the wheel, in another incompatible way?
> DoDi
> _______________________________________________
> fpc-devel maillist  -  fpc-devel at lists.freepascal.org
> http://lists.freepascal.org/mailman/listinfo/fpc-devel

More information about the fpc-devel mailing list