[fpc-devel] Unicode support (yet again)

Flávio Etrusco flavio.etrusco at gmail.com
Mon Sep 19 10:27:13 CEST 2011


On Mon, Sep 19, 2011 at 4:36 AM, Marco van de Voort <marcov at stack.nl> wrote:
> In our previous episode, Fl?vio Etrusco said:
>> compatibility feature, and as such should care more about correctness
>> and ease-of-use rather than performance. I thought the endless bugs
>> WRT to char vs codepoint indexes, even in Java-developed software,
>> would buy my argument...
>
> IMHO you are seeking the problems in the tools, while the problem is PEBKAC

I partly agree it's PEBKAC, but why make it easy to get wrong when you
can avoid it? Isn't that the point of Pascal? Isn't that the point of
AnsiStrings? Isn't that the point of strong typed languages in
general?

> The base principle should be to mess with strings as little as possible, in
> that sense you are right.
>
> I don't like the Java/C# way that you have to manually allocate extra
> objects (stringbuilders etc) to get(performant) access to the characters though.

At least we are not tied by bytecode & VM, so I think we can make better ;-)
Is it unthinkable to have the basic/native string type an object?

Best regards,
Flávio



More information about the fpc-devel mailing list