Compiler support for a unicode string is not enough for the LCL.
As long as base classes like TStrings uses ansistrings, the LCL must use a
string type, that does no conversion.
Of course you are right that the RTL needs to be made up accordingly. Maybe TStrings and friends are needed in multiple versions.

Using a string type that dynamically can be used top hold multiple encodings (as discussed here, too) sounds nice, if it does not result in too slow code (due to the necessity of checking for the coding with any operation).

-Michael
_______________________________________________
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel

Reply via email to