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: <15547.62593.122446.381139@bea.com> Date: Tue, 16 Apr 2002 10:53:05 +0100 To: cygwin AT cygwin DOT com Subject: RE: [PATCH] gettimeofday time travels In-Reply-To: References: Robert Collins writes: > > -----Original Message----- > > From: Philip Aston [mailto:paston AT bea DOT com] > > Sent: Tuesday, April 16, 2002 6:30 PM > > To: cygwin AT cygwin DOT com > > Subject: Re: [PATCH] gettimeofday time travels > > > > > > I'm no W32 expert but: > > Become one. :]. Seriously - the documentation you need is on MSDN. > Search for FileTime and follow your nose. To be fair I'd already done this. Still, I went and had another look and I have to say that IMHO the QueryPerformance* calls aren't really designed for maintaining system time in the way that gettimeofday does. They are designed for accurately measuring small time periods and certainly don't take into account the effects of system time changes or my suspend/resume issue. I guess the reason these calls were introduced in the first place was to support more accurate times. Having done my homework, my fix looks less dirty and I can't think of other approaches except reverting the use of QueryPerformance*. - 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/