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: g2news1.google.com!news2.google.com!news1.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!t-online.de!inka.de!peernews!news.belwue.de!newsfeed.arcor.de!newsspool3.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> <6qottgFdsslcU1@mid.individual.net> Date: Tue, 16 Dec 2008 09:50:37 +0100 Message-ID: <18ckfnjlu93l4$.1fpoya8h7dsm7$.dlg@40tude.net> NNTP-Posting-Date: 16 Dec 2008 09:50:38 CET NNTP-Posting-Host: e002c758.newsspool3.arcor-online.net X-Trace: DXC=C=oOV<[AWZS[7Non7UCi8UMcF=Q^Z^V3X4Fo<]lROoRQ^YC2XCjHcbY_>;:69m`jGYDNcfSJ;bb[UFCTGGVUmh?TLK[5LiR>kgRjHg>HW_m5hX X-Complaints-To: usenet-abuse@arcor.de Xref: g2news1.google.com comp.lang.ada:3006 Date: 2008-12-16T09:50:38+01:00 List-Id: On Tue, 16 Dec 2008 06:50:40 +0100, Wilhelm Spickermann wrote: > Dmitry A. Kazakov wrote: > >> 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." > > Yes, it does not specify a point in time -- but it will do. Where you know that from? > We need it, because someone in some plant has to specify a report > to be printed on the 1-jul-2009 00:00 UTC. You cannot tell him, > that he should wait a month from now until the IERS has > published it's decision about leap second insertion at the end > of next June. No we don't. You cannot show a code that neither: 1. Waits a fixed amount of time (delay until) 2. Periodically polls actual time (delay delta, look at the time). There is simply no other way to determine if the report has to be printed. In either case you don't need another "time." It can be shown even simpler, printing is an action in real time. You cannot present any physical action that happens in political time. Political fictions are incomputable. (:-)) -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de