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,ee78aab9bfd2fe2a X-Google-Attributes: gid103376,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news1.google.com!npeer03.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!cyclone1.gnilink.net!gnilink.net!nx01.iad.newshosting.com!newshosting.com!newsfeed.icl.net!newsfeed.fjserv.net!newsfeed00.sul.t-online.de!t-online.de!tiscali!newsfeed1.ip.tiscali.net!feeder1-2.proxad.net!proxad.net!feeder2-2.proxad.net!newsfeed.arcor.de!newsspool1.arcor-online.net!news.arcor.de.POSTED!not-for-mail From: "Dmitry A. Kazakov" Subject: Re: Inspiration for a better calendar package? Newsgroups: comp.lang.ada User-Agent: 40tude_Dialog/2.0.15.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: <873agxd6i1.fsf@nbi.dk> <12gqldae49yoe$.1sf2zlz1fthvh.dlg@40tude.net> <6qmg8dFd8kd2U1@mid.individual.net> <1jv16tgrmhor4$.c3a8ugjxu6ed$.dlg@40tude.net> <6qn2kmFdflp2U1@mid.individual.net> Date: Mon, 15 Dec 2008 14:46:16 +0100 Message-ID: NNTP-Posting-Date: 15 Dec 2008 14:46:17 CET NNTP-Posting-Host: eadd7fec.newsspool4.arcor-online.net X-Trace: DXC=JTIm=U1PD2K02Sh8E_NfIA4IUKkgBbU?8lS5L9XE X-Complaints-To: usenet-abuse@arcor.de Xref: g2news2.google.com comp.lang.ada:3966 Date: 2008-12-15T14:46:17+01:00 List-Id: On Mon, 15 Dec 2008 13:59:02 +0100, Wilhelm Spickermann wrote: > On the other hand, we can make an appointment for the > 17-aug-2023, 10:00 UTC and this is also a somehow clearly > specified point in time, as we would be able to meet at that > time. No we cannot. 17-aug-2023, 10:00 UTC has no meaning. We don't know if this date will ever exist. > But no one is able to convert this specification to > a "real time" now. (That's why I refuse to call it UTC.) This specification does not specify time. It is a text pattern which may match or not some time point(s) in the future. It exactly same as "when leaves will turn red." > The resolution of "one nominial minute" (_not_ a physical unit) > for wall clock time was chosen, because it's the finest usable > resultion. We can tell that we have 4 nominal minutes between > 31-dec-2044 23:59:58 and 01-jan-2045 00:00:02. But we cannot > express this difference in seconds (or in the physical unit "one > minute"). We will hopefully be able to do that in summer 2044 or > perhaps earlier, when the leap seconds are eliminated. Minute is a physical unit. Political minute is not. We just do not need the latter, because it does not satisfy some fundamental requirements of a physical unit, like anisotropy in 4D space. Why bother with it then? -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de