From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-0.3 required=5.0 tests=BAYES_00,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,a447112bc8b81379
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news4.google.com!news.glorb.com!easynet-monga!easynet.net!newsfeed.arcor.de!news.arcor.de!not-for-mail
From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Subject: Re: Ada, games and frame rate calculation
Newsgroups: comp.lang.ada
User-Agent: 40tude_Dialog/2.0.14.1
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Reply-To: mailbox@dmitry-kazakov.de
Organization: cbb software GmbH
References: 
 <pan.2005.02.16.21.32.06.857696@n_o_p_o_r_k_a_n_d_h_a_m.abyss2.demon.co.uk>
 <mailman.147.1108592182.527.comp.lang.ada@ada-france.org>
 <pan.2005.02.16.23.03.19.256588@n_o_p_o_r_k_a_n_d_h_a_m.abyss2.demon.co.uk>
 <mailman.148.1108601724.527.comp.lang.ada@ada-france.org>
Date: Thu, 17 Feb 2005 09:39:39 +0100
Message-ID: <1g9cglm0ubdz2.d1kk86j8g5xz.dlg@40tude.net>
NNTP-Posting-Date: 17 Feb 2005 09:37:16 MET
NNTP-Posting-Host: bfa45116.newsread2.arcor-online.net
X-Trace: 
 DXC=YilmUi_Vl[=gL1_>^S7Mi=Q5U85hF6f;4jW\KbG]kaM8ea\9g\;7Nm5S5MJIjbEYg4[6LHn;2LCV>7enW;^6ZC`4<=9bOTW=MN>
X-Complaints-To: abuse@arcor.de
Xref: g2news1.google.com comp.lang.ada:8373
Date: 2005-02-17T09:37:16+01:00
List-Id: <comp.lang.ada>

On 16 Feb 2005 19:55:02 -0500, Stephen Leake wrote:

> "Luke A. Guest" <laguest@n_o_p_o_r_k_a_n_d_h_a_m.abyss2.demon.co.uk> writes:
> 
>> It's portable, so yeah there will be a windaz build. My main development
>> platform is Linux. I'm surprised that the win32 is identical to Calendar,
>> well not that surprised ;-) just as long as I can get milliseconds from it
>> then that'll be fine. 
> 
> You can read the clock with microsecond precision (on Windows and some
> other platforms); you can only delay with an accuracy of about 10
> milliseconds (again on Windows).

This is a tunable parameter which default setting depends on the windows
version. It is 10ms under NT. I am not sure about XP, but it seems to be
about 1ms there.

Anyway, an application can screw it up to 1ms. The corresponding Win32 API
is timeBegPeriod. (It is a system-wide setting, BTW! (:-))

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de