[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: mingw32 and sockets

From: Conrad T. Pino
Subject: RE: mingw32 and sockets
Date: Tue, 27 Sep 2005 12:12:22 -0700

> From: Derek Price
> Sent: Tuesday, September 27, 2005 07:43
> This is basically what CVS has been using for a long time.  We are now
> proposing adding, basically:
> #ifdef _WIN32
> # define sock_select   select
> # define fd_select wnt_select
> #else
> # define sock_select select
> # define fd_select select
> #endif
> And defnining wnt_select such that it can differentiate between a file
> and a pipe and make the correct choice about what to do.  I have yet to
> hear for sure if this is possible, though I think Conrad Pino, the
> developer working on it, currently thinks it is.

Definitely possible.

I suggest avoiding "wnt_select" in favor of either "wnt_fd_select" or
"woe32_fd_select" instead.

> >Do you like that? Or better pure POSIX?
> A pure POSIX set of wrappers would be nice, but I'm not sure how to do
> it without wrapping nearly all the low-level IO routines like Cygwin did.

In a prior message I suggested wrapping Microsft C Run Time (CRT) functions
to expose the Win32 API number space but it can go the other direction.

Wrapping the Windows Socket API to integrate sockets into the CRT number
space might work but I have no idea just how much wrapping must be done.

> Regards,


> Derek


reply via email to

[Prev in Thread] Current Thread [Next in Thread]