Michael Schnell schrieb:
With a future "NewStrings" implementation I mean a dynamically coded string typed that can hold e.g. "ASCII code page xxxx", "UTF8", "UTF16", or "UTF32" content and knows about what is stored and how.
How would you determine the byte count for reading and writing text?
So "Length" with this type can be defined as "character count" and copy can work on character length and position, and automatically convert strings if they are coded differently.
I don't like automatic string conversion, because:
Of course certain operations might be really slow if the encoding of the data is not appropriate.
Consider what will happen when every procedure or component has its *own* idea of the "appropriate" encoding...
DoDi -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
