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,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 2002:ac8:65d1:: with SMTP id t17mr7924894qto.302.1583424670354; Thu, 05 Mar 2020 08:11:10 -0800 (PST) X-Received: by 2002:a05:6830:46:: with SMTP id d6mr7395004otp.81.1583424669925; Thu, 05 Mar 2020 08:11:09 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!news.gegeweb.eu!gegeweb.org!usenet-fr.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Thu, 5 Mar 2020 08:11:09 -0800 (PST) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: google-groups.googlegroups.com; posting-host=47.185.239.228; posting-account=zwxLlwoAAAChLBU7oraRzNDnqQYkYbpo NNTP-Posting-Host: 47.185.239.228 References: User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <0b441902-3a20-4cd9-99cd-d0ed71aace81@googlegroups.com> Subject: Re: Ada.Calendar.Formatting.Image (or Time_Of) changing the time From: Optikos Injection-Date: Thu, 05 Mar 2020 16:11:10 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Xref: reader01.eternal-september.org comp.lang.ada:58174 Date: 2020-03-05T08:11:09-08:00 List-Id: On Wednesday, March 4, 2020 at 4:33:12 PM UTC-6, Optikos wrote: > On Tuesday, March 3, 2020 at 5:49:35 PM UTC-6, Randy Brukardt wrote: > > "Simon Wright" wrote in message=20 > > news:lyv9nl8p6w.fsf@pushface.org... > > ... > > > There was a conversation on Ada-Comment in June last year, in which i= t > > > turned out that compiler implementers may have have been misinterpret= ing > > > the ARM. It was quite confusing. > >=20 > > Not just a conversation, but also a Binding Interpretation AI (which=20 > > therefore applies to Ada 2012 compilers), AI12-0336-1. >=20 > Shouldn't these Binding AIs that take effect from a past edition of the I= SO standard onward (and not > merely incorporated into Ada 2020 or Ada 202X post-2020) =E2=80=A2=E2=80= =A2be an ISO/IEC corrigendum=E2=80=A2=E2=80=A2? Allowing > errata be permanently published semi-officially in any forum other than c= ummulatively in an official > ISO/IEC corrigendum seems to be against the ISO/IEC rules. I shouldn't have used the term =E2=80=9Cerrata=E2=80=9D there because it is= a term-of-art for nontechnical grammatical/spelling errors and the minor l= ike. I should have utilized =E2=80=98technical defect=E2=80=99 or some suc= h term instead, because technical defects go in a corrigendum whereas purel= y-linguistic errors go in errata. The ambiguity of UTC vis a vis offsets t= herefrom in past editions of the ISO/IEC Ada standard are a defect in the m= eaning, not a mere linguistic-/syntactic-oops erratum. https://blog.ansi.org/2016/09/standards-changes-amendment-corrigendum-errat= a