From: noer@cygnus.com (Geoffrey Noer) Subject: Re: Sockets in gnu-win32 24 Nov 1996 14:10:51 -0800 Sender: daemon@cygnus.com Approved: cygnus.gnu-win32@cygnus.com Distribution: cygnus Message-ID: <199611242044.MAA20139.cygnus.gnu-win32@cirdan.cygnus.com> Content-Type: text Original-To: miguelb@omega.lncc.br (Fabricio Chalub) Original-Cc: gnu-win32@cygnus.com In-Reply-To: <329786AE.4921@omega.lncc.br> from "Fabricio Chalub" at Nov 23, 96 08:20:15 pm X-Mailer: ELM [version 2.4 PL23] Content-Length: 1044 Original-Sender: owner-gnu-win32@cygnus.com Fabricio Chalub taps on the keyboard: > > The sockets support in gnu-win32 works just fine, but is standing on the > thin ice... for example, some functions are missing, some headers points > to void and some functions are mapped in a poor way... in > , we have this lovely---what should I call---workaround: > > #define socket cygwin32_socket > > which of course maps the BSD API to a function that in turn probably > calls the Winsock32 API (too many function calls, but I guess that's > normal when one maps some system into another.) [...] The way sockets work, we export socket-related functions in the cygwin.dll as cygwin32_funcname and then use defines to map these names to the ordinary ones. In normal use, you will get the cygwin32 sockets. However, if you choose to use WinSock, you can do so without giving up access to the rest of the Cygwin32 API simply by not including the header. If anyone can think of a better way of doing this, please let me know... -- Geoffrey Noer noer@cygnus.com - For help on using this list, send a message to "gnu-win32-request@cygnus.com" with one line of text: "help".