Error codes - errno, h_errno & WSAGetLastError
Error codes set by Windows Sockets are NOT made available via the errno variable. Additionally, for the
getXbyY class of functions, error codes are NOT made available via the h_errno
variable. Instead, error codes are accessed by using the
WSAGetLastError function. This function is provided in Windows Sockets as a precursor (and eventually an alias) for the Win32 function
GetLastError. This is intended to provide a reliable way for a thread in a multi-threaded
process to obtain per-thread error information.
For compatibility with BSD, an application may choose to include a line of the
form:
#define errno WSAGetLastError
This will allow networking code which was written to use the global errno to
work correctly in a single-threaded environment. There are, obviously, some
drawbacks. If a source file includes code which inspects errno for both socket and
non-socket functions, this mechanism cannot be used. Furthermore, it is not
possible for an application to assign a new value to errno. (In Windows Sockets the function
WSASetLastError may be used for this purpose.)
TYPICAL BSD STYLE:
r = recv(...);
if (r == -1
&& errno == EWOULDBLOCK)
{...}
PREFERRED STYLE:
r = recv(...);
if (r == -1 /* (but see below) */
&& WSAGetLastError == EWOULDBLOCK)
{...}
Although error constants consistent with 4.3 Berkeley Sockets are provided for
compatibility purposes, applications should, where possible, use the "WSA"
error code definitions. This is because error codes returned by certain WinSock
routines fall into the standard range of error codes as defined by Microsoft C.
Thus, a better version of the above source code fragment is:
r = recv(...);
if (r == -1 /* (but see below) */
&& WSAGetLastError == WSAEWOULDBLOCK)
{...}
This specification defines a recommended set of error codes, and lists the
possible errors that can be returned as a result of each function. It may be the
case in some implementations that other Windows Sockets error codes will be
returned in addition to those listed, and applications should be prepared to handle
errors other than those enumerated under each function description. However
Windows Sockets will not return any value that is not enumerated in the table of
legal Windows Sockets errors given in the section
Error Codes.
- Software for developers
-
Delphi Components
.Net Components
Software for Android Developers
- More information resources
-
MegaDetailed.Net
Unix Manual Pages
Delphi Examples
- Databases for Amazon shops developers
-
Amazon Categories Database
Browse Nodes Database