On Sat, 4 Oct 2014, Jürgen Hestermann wrote:
In my programs I use this code quite often:
SysErrorMessage(GetLastError);
A closer look at SysErrorMessage shows that the ERRORCODE will
not be used in this routine but only handed over to
FormatMessageA which expects a DWORD!
Am 2014-10-05 um 12:10 schrieb Michael Van Canneyt:
Not necessarily, because it is a cross-platform function and on other systems
the error codes are not necessarily positive values.
Unfortunately, this kind of windows-api-creep is found throughout the RTL.
The proper procedure is probably to
But the current situation is wrong for *all* plattforms
FormatMessage doesn't exist on non-Windows platform. SysErrorMessage doesn't
call FormatMessage on Linux for instance.
--
View this message in context:
Hi list,
Is there any example about how to build a synchronous TCP server using
fcl-net?
Regards
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
Am 05.10.2014 12:28 schrieb Jürgen Hestermann juergen.hesterm...@gmx.de:
Am 2014-10-05 um 12:10 schrieb Michael Van Canneyt:
Not necessarily, because it is a cross-platform function and on other
systems the error codes are not necessarily positive values.
Unfortunately, this kind of
Am 2014-10-05 um 19:04 schrieb leledumbo:
But the current situation is wrong for *all* plattforms
FormatMessage doesn't exist on non-Windows platform. SysErrorMessage doesn't
call FormatMessage on Linux for instance.
Then it would make even less sense to use INTEGER in SysErrormessage.
The
