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.4 required=5.0 tests=AC_FROM_MANY_DOTS,BAYES_00
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,cb2591a9113d8ee6
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII
Path: 
 g2news1.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!news.tiscali.de!not-for-mail
From: Wilhelm Spickermann <zulo.20.unbenutzbar@spamgourmet.com>
Newsgroups: comp.lang.ada
Subject: Re: Advice on Calendar.Time
Date: Wed, 09 Nov 2005 06:23:10 +0100
Organization: Tiscali Germany Usenet
Message-ID: <dks13u$dih$1@ulysses.news.tiscali.de>
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>
 <1131488015.125345.26100@o13g2000cwo.googlegroups.com>
NNTP-Posting-Host: p83.129.11.151.tisdip.tiscali.de
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 8Bit
X-Trace: ulysses.news.tiscali.de 1131513790 13905 83.129.11.151 (9 Nov 2005
 05:23:10 GMT)
X-Complaints-To: abuse@tiscali.de
NNTP-Posting-Date: Wed, 9 Nov 2005 05:23:10 +0000 (UTC)
User-Agent: KNode/0.8.0
Xref: g2news1.google.com comp.lang.ada:6317
Date: 2005-11-09T06:23:10+01:00
List-Id: <comp.lang.ada>

REH wrote:

>> 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.

Really? There is no possibility to specify any point in time
during the positive leap second and there is no possibility to
have a meaningful time stamp there. And all time differences
between times before and times after the leap second will be
wrong. (The clock just stops running for a second, pretending
that this second doesn't exist -- very much like an analog wall
clock.) 

>�It's�consistant.��

In itself -- yes. But it's not consistant with the clock in the
embedded system as that one counts (presumably) every second of
reality. But if you can live with that -- ok.

> ... and how to force it to use GMT or UTC.

In systems of the Unix family, it may suffice to set the TZ
environment variable for the image to be startet. In my
GNU/Linux I would start the program X with: "TZ=UTC X".

Wilhelm