From: sos@prospect.com.ru (Sergey Okhapkin)
Subject: RE: sys/socket #define problems
1 Sep 1997 21:03:57 -0700
Sender: mail@cygnus.com
Approved: cygnus.gnu-win32@cygnus.com
Distribution: cygnus
Message-ID: <01BCB6DB.65569F40.cygnus.gnu-win32@gater.krystalbank.msk.ru>
Original-To: "gnu-win32@cygnus.com" <gnu-win32@cygnus.com>,
        "'Graham Dumpleton'"
	 <Graham.Dumpleton@nms.otc.com.au>
Encoding: 22 TEXT
Original-Sender: owner-gnu-win32@cygnus.com

Graham Dumpleton wrote:
> In sys/socket.h, there exists a whole bunch of #define's like:
>
> #define bind cygwin32_bind
> ..
>
> The intent is to ensure that the Win32 versions of these functions are 
not
> used. Can some other way be found of doing this, or for C++ at least, can
> they be made into C++ inline functions.

These nasty defines are not needed at all... The winsock versions will not 
be used until you don't include <winsock.h> - the win32 versions has 
stdcall names (like socket@4), but cygwin/unix versions has ordinary names. 
I've wrote about to cygnus, no answer... Cygwin32_ prefixes fools many 
configure scripts :-(

--
Sergey Okhapkin, http://www.lexa.ru/sos
Moscow, Russia
Looking for a job.


-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
