Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-ID: <3CA35209.DF78CD8D@sacet.com> Date: Thu, 28 Mar 2002 18:25:29 +0100 From: Herve Bailly Organization: SACET X-Accept-Language: fr MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Time function implementations for cygwin References: <3CA325D4 DOT E284A9F4 AT sacet DOT com> <20020328153817 DOT GE11781 AT redhat DOT com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hello, My question was bad asked. Time functions are very usefull for my application. And I would like to know if time functions are not implemented because of unsovable problems with Windows or if they will be implemented in a near feature. Thank you for any response. Herve BAILLY Christopher Faylor a écrit : > On Thu, Mar 28, 2002 at 03:16:52PM +0100, Herve Bailly wrote: > >I would like to know if functions like "clock_gettime", "clock_getres", > >"nanosleep", time_out for "select" or "sem_wait" functions, are > >implemented in CYGWIN. > > This is your second message on the subject. It's easy enough to figure > this out for yourself. Why do you need someone to tell you yes or no? > > For the record, clock_*, nanosleep, and time-out are not implemented. > > cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/