[fpc-devel] Unicode resource strings

Mattias Gaertner nc-gaertnma at netcologne.de
Tue Aug 21 15:13:27 CEST 2012

On Tue, 21 Aug 2012 13:53:14 +0100
Graeme Geldenhuys <graemeg.lists at gmail.com> wrote:

> On 21 August 2012 13:03, Michael Schnell <mschnell at lumino.de> wrote:
> > With "not so often" I meant program runtime:  it is usually not called in a
> > close long running loop.
> I have a program that does exactly that... Loads files to do CRC
> checking to see what changed. It's a recursive find-all that goes
> through 100k or more files. It's already a slow process on non-SSD
> drives processing 12GB or more of data, so adding the multiple
> unnecessary string conversions which will be enforced on Linux users
> would make that even worse. For me, every optimisation counts.

Then you would not use TStrings in the first place.

> With some simple trials in various projects I can clearly see a
> Unicode RTL with one string type, and native encoding on each platform
> as very plausible. 

One string type and native encoding. Do you mean the current AnsiString?

I guess you mean UTF-16/UTF-8 depending on platform. That would be
different character sizes, which means lots of IFDEFs in users code.


More information about the fpc-devel mailing list