IMO, I wouldn't support wide-character (UnicodeString) strings for anything
new.
In the beginning the wide-character string had the advantage of being able
to represent
all characters with 2 bytes, but this is no longer the case. I would switch
to UTF-8
instead and keep characters 1 byte long. A switch to UTF-8 only affects a
small amount of the code-base, and doesn't break string references.
In fact, I introduced UTF-8 in my OS recently, and it was easy to do. So not
supporting wide-character strings does not mean you must keep an old
ansi state.
Leif Ekblad
----- Original Message -----
From: "Hans-Peter Diettrich" <drdiettri...@aol.com>
To: "FPC developers' list" <fpc-devel@lists.freepascal.org>
Sent: Sunday, December 23, 2012 5:49 AM
Subject: Re: [fpc-devel] Forwarded message about FPC status
Graeme Geldenhuys schrieb:
Well, let me just say that the idea of two RTL's is rather ridiculous
too!!
It's not different from Delphi, where the introduction of UnicodeString
required a renewed RTL, VCL and IDE. Who should do the same for FPC and
Lazarus, and tell the users that they either have to stay with an old
(frozen) Ansi release, or must upgrade all their code and component
libraries to the new strings, RTL and LCL? IMO a typical loose-loose
situation :-(
Anyway, I can see where this thread is heading... just another waist of
time. So I'll stop here.
Yeah
DoDi
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
