From:	miguelb AT omega DOT lncc DOT br (Fabricio Chalub)
Subject:	Sockets in gnu-win32
23 Nov 1996 15:58:51 -0800 :
Sender:	daemon AT cygnus DOT com
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<329786AE.4921.cygnus.gnu-win32@omega.lncc.br>
Mime-Version:	1.0
X-Mailer:	Mozilla 3.01Gold (Win95; I)
Original-To:	gnu-win32 AT cygnus DOT com
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

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
<sys/socket.h>, 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.)

Ok, I am creating a C++ class which encapsulates BSD socket's
functionality in a object-oriented manner (just for study/fun, I
guess... who can separate these things in computer science?). It's
called wormHole.  One of its members is wormHole::socket().  Now guess
what happened when I compiled my source file!  Let cc1plus take the
word:

wormHole.cpp: In method `wormHole::wormHole(char *, int)':
wormHole.cpp:18: too many arguments for method `int
wormHole::cygwin32_socket()'

some dirty little hack is needed here... :|

[]s fabricio chalub
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -