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

Tomas Hajny XHajT03 at hajny.biz
Wed Feb 8 13:08:30 CET 2012

On Mon, February 6, 2012 17:39, Felipe Monteiro de Carvalho wrote:
> Hello,
> SysUtils for Windows utilizes only A Windows APIs, while it could use
> W APIs in Windows NT. The attached patch starts correcting improving
> the situation.
> Advantages of the patch:
> * Allows for unicode file names in TStringList.LoadFromFile if you
> install paswstrings as the unicode manager.
> Disadvantages of the patch:
> * None that I can imagine.
> Waiting for comments.

Regardless of other points raised in the discussion so far and their
validity or not, there's one more thing not clear to me. Your patch
suggest to use either *A or *W call depending on a condition evaluated at
run-time. What's the benefit? If your intention was to keep the programs
working with Win9x, this won't help because the program containing
unresolved imports wouldn't start anyway. Is there any other reason?


More information about the fpc-devel mailing list