X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 25 Oct 2007 16:12:30 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: strange select() and recvfrom() behaviour Message-ID: <20071025141229.GR20400@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <52376 DOT 131 DOT 220 DOT 7 DOT 1 DOT 1193317614 DOT squirrel AT webmail DOT iai DOT uni-bonn DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52376.131.220.7.1.1193317614.squirrel@webmail.iai.uni-bonn.de> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Oct 25 15:06, Marcell Missura wrote: > I also find it weird that after an > error occured select() returns and tells you that the socket has something > to _read_. That's documented standard behaviour. I pointed this out in my first reply. If you're still learning socket programming I'd like to suggest this book: http://www.amazon.com/Unix-Network-Programming-Vol-Networking/dp/0131411551/ref=sr_1_1/102-9342001-5959348?ie=UTF8&s=books&qid=1193321471&sr=8-1 It's the socket bible, sort of. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/