Dossy Shiobara wrote:
It's probably safer to define this as SOCKET, but windows.h says
SOCKET is:
The source comment is misleading, because trigger is set up as a socket
pair, not as a pipe. Not sure why it's this way, but there it is. And
ns_sockpair is already prototyped as
ns_sockpair(SOCKET *socks)
so if this is a problem it really should be triggering a compiler
warning about it. In any case, since unix defines SOCKET as int, it
should make zero difference on the unix side to change the structure
definition.
-J
typedef u_int SOCKET;
And:
typedef unsigned int u_int;
Since Windows is LLP64 and most Unix-like systems are LP64, I don't
understand how AOLserver's defining trigger[2] as (int) is the problem
-- Windows might complain about some signed/unsigned thing at compile
time, but in both cases, (int) is 32 bits.
On 8/4/11 3:24 AM, Maurizio Martignano wrote:
int trigger[2]; /* Wakeup trigger pipe. */ ß Why is this an int when
it was a SOCKET (any justification????)
--
Dossy Shiobara | "He realized the fastest way to change
[email protected] | is to laugh at your own folly -- then you
http://panoptic.com/ | can let go and quickly move on." (p. 70)
* WordPress * jQuery * MySQL * Security * Business Continuity *
-- AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
<[email protected]> with the body of "SIGNOFF AOLSERVER" in the
email message. You can leave the Subject: field of your email blank.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
<[email protected]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
