X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 10 Feb 2010 22:06:24 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Bug: select() does not modify timeout (arg 5) on return Message-ID: <20100211030624.GB2654@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <790762 DOT 40188 DOT qm AT web35906 DOT mail DOT mud DOT yahoo DOT com> <4B7371EF DOT 90607 AT byu DOT net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B7371EF.90607@byu.net> User-Agent: Mutt/1.5.20 (2009-06-14) 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 Wed, Feb 10, 2010 at 07:56:47PM -0700, Eric Blake wrote: >According to Javier on 2/10/2010 3:29 PM: >> select() call with specified timeout in argument 5 is not altered on return when time is up. >> >> on windows code below returns: should be 0.0 but we have: 5.0 >> on linux code below returns: should be 0.0 but we have: 0.0 > >For Linux compatibility, it would be nice to alter the argument. But >POSIX is clear that the current cygwin behavior of leaving the argument >unchanged is also compliant. I believe actually made a conscious decision not to alter the arguments when I first wrote select(). However, times have changed so it probably makes sense to alter it to be more linux-like now. I'll look into doing that. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple