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,e686c2c95beefb1c
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news1.google.com!news.glorb.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local1.nntp.dca.giganews.com!nntp.megapath.net!news.megapath.net.POSTED!not-for-mail
NNTP-Posting-Date: Tue, 24 Aug 2004 14:24:23 -0500
From: "Randy Brukardt" <randy@rrsoftware.com>
Newsgroups: comp.lang.ada
References: <MPG.1b7c58269c53dcbc9897db@news.individual.net>
 <br8nmj3ulp8n$.1hmfh3p3izvj8$.dlg@40tude.net>
 <ceu88b$lo5$1@sparta.btinternet.com>
 <1jgik0ntrex36$.1pyha1husddpe.dlg@40tude.net>
Subject: Re: Inserting Calendar.Time in a database
Date: Tue, 24 Aug 2004 14:25:19 -0500
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Message-ID: <psOdnQOXyd96CLbcRVn-oQ@megapath.net>
NNTP-Posting-Host: 64.32.209.38
X-Trace: 
 sv3-P4vXfpzrRmj3EHBy8fzdQvim5EclW8cGja8LFgIzUnYFM95YPTc36SZ/4W1Xd0rExj47DXyc89JRiB6!mIxx7TWNGhqOWe36FRmfjNi+w+/T19SsepVLnyZR4pmf5/d9bbYOta6kshrD9KYS44AczrawbgU/
X-Complaints-To: abuse@megapath.net
X-DMCA-Complaints-To: abuse@megapath.net
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint
 properly
X-Postfilter: 1.3.13
Xref: g2news1.google.com comp.lang.ada:2970
Date: 2004-08-24T14:25:19-05:00
List-Id: <comp.lang.ada>

"Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> wrote in message
news:1jgik0ntrex36$.1pyha1husddpe.dlg@40tude.net...
...
> I see a problem with it. UTC_Time_Offset is not constant, so there also
> should be an atomic way to get exact UTC. Actually Ada.Real_Time.Time
seems
> a better candidate for UTC. I would add it there.

This is a gross misunderstanding of Ada's clock packages. Ada.Calendar is
about time related to an external (standard) timebase, like UTC or CDT.
Ada.Real_Time is about time related to an internal timebase. There is no
defined relationship between Calendar and Real_Time, and that's intentional.
Real_Time would typically be implemented with a hardware counter (such as
QueryPerformanceCount on Windows).

Moreover, Ada.Real_Time has no concept of dates, which is critical to using
a UTC time. Adding all of that to Ada.Real_Time would just make it a clone
of Calendar, which then would beg the question of why we need two different
time packages.

> It is not warranted [guarenteed] that Clock /= Clock.

Of course. How could it be? If two calls are sufficiently close together,
the clock may not have ticked in the interval. That's true even for
Ada.Real_Time.Clock; it only guarantees never to run backwards.

                            Randy.