On 02.08.2017 09:29, Michael Van Canneyt wrote:
FPC "forces" nothing. It offers a single-byte string TStrings
implementation.
If you want to use that for Unicode, you indeed have no choice but to
use UTF8
or use/write a separate class that uses UTF16.
That is why I said that it is less silly ! :)
But it does force TStrings siblings to handle single-byte strings (While
Delphi forces TStrings siblings to handle 16-bit-word Strings).
As a huge count of classes in the RTL (and the LCL and MSEGUI and ...,
and in user code) are or use TStrings siblings the compatibility issues
and certain other problems are due to happen.
(I hope I will not completely banned now, as I already am under
monitoring for this kind of posts...)
-Michael
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
