[fpc-devel] Is calling the Windows Unicode APIs really faster than the ANSI API's?
Marco van de Voort
marcov at stack.nl
Fri Sep 26 13:10:17 CEST 2008
In our previous episode, Daniël Mantione said:
> > Taking a step back from Free Pascal and Tiburon.... How do other
> > frameworks handle string encodings etc... Frameworks like Java, Qt
> > etc... Can't we learn something from them as well? Both Java and Qt
> > run on multiple platforms, read/write to files, do string manipulation
> > etc.... I don't know those frameworks well, but they have huge
> > developer base and backed by huge companies (with plenty of developers
> > working on those frameworks). Plus, they have been supporting Unicode
> > for ages already! I'm sure we can learn something from their
> > experience.
>
> Both Java & QT use UTF-16 internally.
Afaik Java and .NET (C#) also have the feature that for character based
access you need to use a different type (a -builder type).
This means they can have separate internal encodings for the base string
type, and the chara based editing string types.
More information about the fpc-devel
mailing list