On 11/25/2014 09:39 PM, Hans-Peter Diettrich wrote:
The Delphi model already broke that claimed type safety, by omitting conversions of RawByteString results, for speed optimization. That's dangerous, because the compiler can *only* check the static type of string variables, but not the dynamic encoding of their contents.... This was clear to me just after exploring and understanding encoded strings in Delphi. In FPC/Lazarus we now have a *chance* for simplifications and improvements, when the new features are used in the *right* way.
On that behalf I just posted a set of questions on the "FPC Unicode support" wiki page in the fpc-devel mailing list. Please continue this discussion there.
But many arguments and opinions, presented in this thread, indicate to me an yet incomplete understanding and many misunderstandings, which I actually try to spot.
See the new wiki page http://wiki.freepascal.org/not_Delphi_compatible_enhancement_for_Unicode_Support
-Michael -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
