Re: The "black magic" of ioctl

["Frank J. Lhota" <FrankLho.NOSPAM@rcn.com>]

On 10/24/2010 2:36 PM, Simon Wright wrote:
> Florian Weimer<fw@deneb.enyo.de>  writes:
>
> I hadn't realised this: but a quick scan of the GNAT sources confirms:
> in socket.c,
>
> * Wrapper for ioctl(2), which is a variadic function */
>
> int
> __gnat_socket_ioctl (int fd, int req, int *arg) {
> #if defined (_WIN32)
>    return ioctlsocket (fd, req, arg);
> #else
>    return ioctl (fd, req, arg);
> #endif
> }

This is because of a Microsoft portability problem; in Winsock (the 
windows socket facility), the function for performing ioctl on sockets 
is named ioctlsocket instead of ioctl. This is one of many areas where 
Winsock differs just enough from the standards to require heavy use of 
"#if" preprocessing directives to maintain portability. This is why 
Winsock is by far my least favorite part of the Win32 API. At any rate, 
this problem is not an Ada issue.

-- 
"All things extant in this world,
Gods of Heaven, gods of Earth,
Let everything be as it should be;
Thus shall it be!"
- Magical chant from "Magical Shopping Arcade Abenobashi"

"Drizzle, Drazzle, Drozzle, Drome,
Time for this one to come home!"
- Mr. Wizard from "Tooter Turtle"