On 01/06/2012 11:42 AM, Hans-Peter Diettrich wrote:
You instead argue based on half-baked ideas, so please stay away from
calling other models "insane" :-]
I never promoted that the compiler should force us to _always_ make use
of the features that are provided by dynamically encoded strings. I only
promote the idea that if FPC indeed implements dynamically encoded
strings, we should provided with the possibility to make fully use of
them if we choose to do so (e.g. by writing a (library) function that
can accept any encoding type and does not do any conversion, neither on
entry or exit, nor while working with the strings).
If used decently this will not slow down, but in many cases speed up the
code.
Of course this right now is half-baked, as the discussion about the
functionality in detail had been killed with the argument that Delphi
dopes not provide this.
The insane stuff mentioned here was the Length of a AnsiString(1200)
that Swen claimed Delphi XE calculates (I can't test it). and this
obviously is insane (or half-baked) in Delphi.
-Michael
_______________________________________________
fpc-devel maillist - [email protected]
http://lists.freepascal.org/mailman/listinfo/fpc-devel
