Am 06.01.2012 10:19, schrieb Michael Schnell:
On 01/06/2012 09:59 AM, Marco van de Voort wrote:
Unicodestring.
Of course this is "suggested" regarding the history of Delphi, before
the variable string type had been introduced.
But again, even the name now is ambiguous, as there are several Unicode
encoding types and they seem to be available with the new string type.
(This is what this discussion is about.) If UnicodeString forces UTF-16
encoding, why not use a more "speaking" name ?
And again, this seems not "sane", again (so it maybe is questionable if
it makes sense to adopt the paradigm to FPC) . Why provide yet another
type of strings, if we have a string type that is able to hold 1- 2- and
4- byte based encoding types including any variants of those ?
I don't know about Delphi, but in FPC the UnicodeString type existed
before the code page aware String type was merged (the first release
with it was 2.4.0 AFAIK). Also there is the usual reason for unintuitive
implementations: Delphi compatibility.
Regards,
Sven
_______________________________________________
fpc-devel maillist - [email protected]
http://lists.freepascal.org/mailman/listinfo/fpc-devel
