[fpc-devel] Encoded AnsiString

Michael Schnell mschnell at lumino.de
Tue Jan 7 11:34:29 CET 2014

On 01/07/2014 11:22 AM, Michael Van Canneyt wrote:
> There is not much to say.
> There will be 2 sets of units:
> * Unicode
> * AnsiString
> for unicode, there is no problem, since everything is 2 bytes 
> (ignoring some exotic codepoints here) so string encoding does not apply.
> for ansistring, string=ansistring, there are some encoding issues, but 
> the RTL is capable of using Widestrings for all OS interface routines.

This might help in a certain way, but defining a decently dynamic string 
subtype and use same for TStringList would allow for a lot more 
flexibility / functionality. (Together with eliminating the ambiguous 
naming "ANSI...")


More information about the fpc-devel mailing list