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,cb2591a9113d8ee6
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!postnews.google.com!o13g2000cwo.googlegroups.com!not-for-mail
From: "REH" <spamjunk@stny.rr.com>
Newsgroups: comp.lang.ada
Subject: Re: Advice on Calendar.Time
Date: 8 Nov 2005 14:13:35 -0800
Organization: http://groups.google.com
Message-ID: <1131488015.125345.26100@o13g2000cwo.googlegroups.com>
References: <1131465873.702910.143400@g43g2000cwa.googlegroups.com>
   <JHWpIvErQcPT@eisner.encompasserve.org>
   <dkqp1u$62p$1@ulysses.news.tiscali.de>
   <1131475104.101511.297410@g49g2000cwa.googlegroups.com>
   <dkquap$7e8$1@nwrdmz01.dmz.ncs.ea.ibs-infra.bt.com>
   <1131480345.878386.71750@f14g2000cwb.googlegroups.com>
   <dkr7lv$9af$1@ulysses.news.tiscali.de>
NNTP-Posting-Host: 192.35.35.35
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1131488020 8234 127.0.0.1 (8 Nov 2005 22:13:40
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Tue, 8 Nov 2005 22:13:40 +0000 (UTC)
In-Reply-To: <dkr7lv$9af$1@ulysses.news.tiscali.de>
User-Agent: G2/0.2
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.7.12) Gecko/20050915,gzip(gfe),gzip(gfe)
Complaints-To: groups-abuse@google.com
Injection-Info: o13g2000cwo.googlegroups.com; posting-host=192.35.35.35;
   posting-account=lnUIyw0AAACoRB2fMF2SFTIilm8F10q2
Xref: g2news1.google.com comp.lang.ada:6303
Date: 2005-11-08T14:13:35-08:00
List-Id: <comp.lang.ada>


Wilhelm Spickermann wrote:
> REH wrote:
>
> > But I don't think there is anything that is, or should be,
> > OS-dependent with dates and time-of-day, or timezones, or GMT,
> > or UTC, or DST, or leap seconds, etc.  These concepts are well
> > defined and do not change from platform to platform.
>
> I agree. But as the run time system normally depends on the OS
> time services it depends on the configuration of these services.
>
> But even after having the operating system configured in a way
> such that we have no DST and and no posix handling of leap
> seconds, there will be at least one remaining problem:
> Ada.Calendar is inherently POSIX: Day_Duration is too short for
> a leap second and Time_Of called with a seconds value of
> 86_400.0 is forced by ARM 9.6-25 to return the same value as
> Time_Of for the next day with seconds value of 0.0.
>
> Wilhelm

That's fine.  It's consistant.  The problem I am having is that there
is no consistant why to deal with knowing what time zone a particular
Ada implementation uses for Time, and how to force it to use GMT or
UTC.