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 From: "Philip Aston" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15596.2430.79514.567449@bea.com> Date: Wed, 22 May 2002 22:11:25 +0100 To: cygwin AT cygwin DOT com Subject: Re: [PATCH] gettimeofday time travels V2 In-Reply-To: <20020521042938.GA12123@redhat.com> References: <15654 DOT 52373 DOT 497253 DOT 37486 AT bea DOT com> <20020518061802 DOT GA10347 AT redhat DOT com> <15598 DOT 6233 DOT 401150 DOT 171276 AT bea DOT com> <20020521042938 DOT GA12123 AT redhat DOT com> Christopher Faylor writes: > I hate to say this, but after reading various references on the > QueryPerformance* functions, I don't think that we should be using > them. I'm tired and probably hysterical, but this makes me smile. > There was a clamor to implement things this way a few months ago, > and I implemented this to provide improved precision. However, it > looks like I sacrificed accuracy for precision. Others have already > pointed this out and after a google/msdn search I am now convinced. > > I think the best we can probably do is to use the multimedia timer > functions to get 1ms accuracy and I'll be redoing gettimeofday to > use those in the next couple of days. > > I'm *very* sorry for making you jump through hoops. > > If someone wants to step forward to convince me that I'm wrong in > now thinking that the QueryPerformance* functions are bad news, > then please feel free. > > Otherwise, 1.3.11 will have YA implementation of gettimeofday. No worries, it kills me daily - I just want it fixed. Now if there's any other requirements for windows event listeners, I've got just the code... - Phil -- 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/