On 03/05/17 09:52, Graeme Geldenhuys via Lazarus wrote:
[rant]
ps:
Both FPC and Delphi is in such a messed up state when it comes to
string and character types. It is the laughing stock of programming
languages at the moment. At least EMBT is heading in the right
direction with their Linux Delphi compiler - they completely removed
AnsiString.
FPC and Delphi can learn a huge lesson from Java and Qt in how to
handle string and character types.
[/rant]
Regards,
Graeme
Is Delphi/FPC string handling that much worse than 'C'?
To me, the great thing about AnsiString is that it provides unified
handling of UTF8 and legacy codepages in a single managed type by
including the code page id as a dynamic property of the string.
On the other hand, AnsiString and UnicodeString are still separate
types. Why? Why should there not be a single unified string type with
(e.g.) ASCII, UTF8 and UTF-16 (or MS Unicode) being just another code page?
--
_______________________________________________
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
http://lists.lazarus-ide.org/listinfo/lazarus
