Received: from hrndva-omtalb.mail.rr.com (hrndva-omtalb.mail.rr.com [71.74.56.123]) by krbdev.mit.edu (8.12.9) with ESMTP id m6NHPPo4020005; Wed, 23 Jul 2008 13:25:25 -0400 (EDT) Received: from www.secure-endpoints.com ([24.193.47.99]) by hrndva-omta05.mail.rr.com with ESMTP id <20080723172519.CSBL1194.hrndva-omta05.mail.rr.com@www.secure-endpoints.com> for ; Wed, 23 Jul 2008 17:25:19 +0000 Received: from [192.168.1.34] by secure-endpoints.com (Cipher TLSv1:RC4-MD5:128) (MDaemon PRO v9.6.6) with ESMTP id md50000098892.msg for ; Wed, 23 Jul 2008 13:27:11 -0400 X-Spam-Processed: www.secure-endpoints.com, Wed, 23 Jul 2008 13:27:11 -0400 (not processed: message from trusted or authenticated source) X-Mdptrlookup-Result: pass dns.ptr=cpe-24-193-47-99.nyc.res.rr.com (ip=24.193.47.99) (www.secure-endpoints.com) X-Mdhelolookup-Result: hardfail smtp.helo=[192.168.1.34] (does not match 24.193.47.99) (www.secure-endpoints.com) X-Authenticated-Sender: jaltman@secure-endpoints.com X-Return-Path: jaltman@mit.edu X-Envelope-From: jaltman@mit.edu X-Mdaemon-Deliver-To: rt@krbdev.mit.edu Message-ID: <488769EA.1020403@mit.edu> Date: Wed, 23 Jul 2008 13:27:06 -0400 From: Jeffrey Altman User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: rt@krbdev.mit.edu Subject: Re: [krbdev.mit.edu #6041] WIN32 SOCKET != int in gss and rpc libs References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: jaltman@mit.edu RT-Send-Cc: X-RT-Original-Encoding: iso-8859-1 Content-Length: 465 Ken Raeburn via RT wrote: > closesocket returns an int as close does. If we're intentionally > ignoring the return values, please keep the (void) casts, at least for > now. sure although I don't understand why ignoring that return value should be treated specially. > Why do you need to define INVALID_SOCKET in svc_udp.c? INVALID_SOCKET is a special value on Windows which is architecture dependent. Is INVALID_SOCKET defined somewhere else for Unix?