[fpc-devel] Changing Windows API A routines in SysUtils to W in Windows NT

Marco van de Voort marcov at stack.nl
Tue Feb 7 12:07:35 CET 2012

In our previous episode, Felipe Monteiro de Carvalho said:
> No, it will not use UTF-8 by default because that would break
> compatibility. It will use the system encoding by default and you can
> use SetMultiByteConversionCodePage to change it to use UTF-8.

Note that this might sound useful now ansistring without codepage is still
the default string, but if the default string type changes, this is not 
really useful.

IOW it is a short term hack with a long time support burden IMHO.

That being said, I do think we will need to start migrating to the W
versions in time.

But first a proper decision must be made about the default string type, and
such things shouldn't be slipped by the back door. 

More information about the fpc-devel mailing list