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=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,8c564a80b820db35
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.68.134.225 with SMTP id pn1mr1943549pbb.7.1330972248177;
        Mon, 05 Mar 2012 10:30:48 -0800 (PST)
Path: 
 h9ni42952pbe.0!nntp.google.com!news1.google.com!news.glorb.com!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail
From: Simon Wright <simon@pushface.org>
Newsgroups: comp.lang.ada
Subject: Re: Any leap year issues caused by Ada yesterday?
Date: Mon, 05 Mar 2012 18:30:46 +0000
Organization: A noiseless patient Spider
Message-ID: <m2eht6j3xl.fsf@pushface.org>
References: <4f4f746a$0$6565$9b4e6d93@newsspool3.arcor-online.net>
	<abdf6306-50b4-43ed-9e18-3c57c1e97160@9g2000vbq.googlegroups.com>
	<20608866.730.1330963171058.JavaMail.geo-discussion-forums@ynbq18>
	<1t8v4akrmapkl.1xwfi9yxtw2ji$.dlg@40tude.net>
Mime-Version: 1.0
Injection-Info: mx04.eternal-september.org;
 posting-host="dFCm8HWntFqmDIilBLqEJQ";
	logging-data="6250"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX18Fk47rSYBGikgIpeEU6yvjjc7umRhdIAs="
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (darwin)
Cancel-Lock: sha1:7lRh3bGIFMl65Ebwd/QzLnENZyQ=
	sha1:lxDWVQrdWFcj30J0ZnPoD7oF0rw=
Content-Type: text/plain; charset=us-ascii
Date: 2012-03-05T18:30:46+00:00
List-Id: <comp.lang.ada>

"Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> writes:

> BTW, I would not wonder to see Real_Time.Time and Calendar.Time same
> or correlated.

We were surprised and disappointed to find that earlier releases of GNAT
did have them the same. What happens to your precise timing if you get
an NTP update in the middle of it?

OK, this is slightly GNAT-related, since (at that time, anyway) "delay
0.5" translated under the hood into "delay until now + 0.5" on VxWorks,
so you were always related to the actual clock. A different compiler (or
a different OS) might use a different design.

AdaCore accepted the bug report (after we pointed out the "shall" in
ARM95 D.8(32)).

http://www.adaic.org/resources/add_content/standards/95lrm/ARM_HTML/RM-D-8.html