From:	jp AT NuanceCom DOT COM ("J. P. Shipherd")
Subject:	mywinsock.h
8 Jan 1997 14:57:01 -0800 :
Sender:	daemon AT cygnus DOT com
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<199701081902.LAA03167.cygnus.gnu-win32@nuancecom.com>
Mime-Version:	1.0 (generated by tm-edit 7.94)
Original-To:	gnu-win32 AT cygnus DOT com
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

Has anyone used the winsock provided by gnu32? It seems like there are
many strange/missing things.  For example the following is defined on
line 160:

typedef unsigned char   u_char;
typedef unsigned short  u_short;
typedef unsigned int    u_int;
typedef unsigned long   u_long;

/*
 * The new type to be used in all
 * instances which refer to sockets.
 */
typedef u_int           SOCKET;


But this is defined on line 85:

/* Can't export some of these, since they conflict with standard unix stuff */
typedef struct fd_set {
        u_short fd_count;               /* how many are SET? */
        SOCKET  fd_array[FD_SETSIZE];   /* an array of SOCKETs */
} fd_set;

giving an error for undefined u_short and SOCKET types.


Furthmore, much of the standard BSD functions like:

#if 0
int PASCAL FAR ioctlsocket (SOCKET s, long cmd, u_long FAR *argp);
u_long PASCAL FAR htonl (u_long hostlong);
u_short PASCAL FAR htons (u_short hostshort);
u_long PASCAL FAR ntohl (u_long netlong);
u_short PASCAL FAR ntohs (u_short netshort);
int PASCAL FAR shutdown (SOCKET s, int how);


are declared inside #if 0 blocks

Finally, what is the importance of __INSIDE_CYGWIN32__ is?

If anyone has used this stuff or knows of a resource with some info
about how it works I'd appreciate it.  Even a note that says "this
doesn't work, don't try to use it"  would be helpful.

Thanks!
--jp
-
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 -