[fpc-devel] Unicode proceedings
Hans-Peter Diettrich
DrDiettrich1 at aol.com
Wed Nov 16 14:56:06 CET 2011
Michael Schnell schrieb:
> Obviously a system of hard coded string types (such as A) is not what
> everybody (but some) wants (e.g. as there would need a lot of such types
> and because EMB decided implementing dynamic typing).
It's the best system, performance-wise. An application should not use
more than one or two string types, e.g. Delphi uses the native/generic
AnsiString(0), and FPC/Lazarus may add UTF-8 strings. All other Ansi
encodings will only add a lot of conversions, with no added advantage.
> There still are ambiguous cases:
> - "intersexual" variables (strict Typed variable that happens to be
> correctly done but with an encoding that does not match the type name)
This should never occur.
> - RAW variables that in fact have a dynamic encoding definition of
> "NONE/RAW" and are to be converted into a strictly typed variable.
> Handling this might be considered an "implementation detail". So Delphi
> compatibility is not necessary.
Nobody wants that, except you.
DoDi
More information about the fpc-devel
mailing list