[fpc-devel] Save the current FPC UnicodeString!

Florian Klaempfl florian at freepascal.org
Tue Nov 10 10:33:07 CET 2009

> - There is only one encoding in MSEgui framework, it is the same on all 
> platforms.

Which is performance wise neither a good decision.

> - In the majority of cases the fast and convenient character access by index 
> can be used. This is important for beginners.
> - The current FPC UnicodeString is fast, simple, has little overhead and is 
> well tested.
> So please don't destroy this ideal solution by dropping current FPC 
> UnicodeString in favour of the Delphi string which is complicated, 

Who says that? If you don't mess with code pages, the only different
you'll might see is that UnicodeString gets two new fields: encoding and
char size. However, this information is usually only used if you pass
the string to a RawString parameters. Normal Unicodestring routines
initialize these fields and that's it.

> less 
> performant, 

In which regard?

> will have many new bugs and is inscrutable by the average user!
> Please remember how many time it took  to fix WideString. I don't want to go 
> this ordeal again.

More information about the fpc-devel mailing list