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=unavailable autolearn_force=no version=3.4.4 X-Received: by 2002:a24:492a:: with SMTP id z42-v6mr2790ita.55.1523281249489; Mon, 09 Apr 2018 06:40:49 -0700 (PDT) X-Received: by 2002:a9d:3286:: with SMTP id u6-v6mr705479otb.13.1523281249264; Mon, 09 Apr 2018 06:40:49 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!news.unit0.net!peer01.am4!peer.am4.highwinds-media.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!k65-v6no1967724ita.0!news-out.google.com!u64-v6ni3970itb.0!nntp.google.com!k65-v6no1967719ita.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Mon, 9 Apr 2018 06:40:49 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=47.185.233.194; posting-account=zwxLlwoAAAChLBU7oraRzNDnqQYkYbpo NNTP-Posting-Host: 47.185.233.194 References: <1b44444f-c1b3-414e-84fb-8798961487c3@googlegroups.com> <62ee0aac-49da-4925-b9aa-a16695b3fc45@googlegroups.com> <9879872e-c18a-4667-afe5-41ce0f54559f@googlegroups.com> <80db2d05-744f-4201-ba1b-4436f8040491@googlegroups.com> <59f9ab6d-d6ba-45ff-a6f0-c5699983d9e8@googlegroups.com> <1a390e22-f49f-4028-8e58-ca4d0f51e4b6@googlegroups.com> <8fca2fed-2721-48dc-95e5-5b98e7c1fa70@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Interesting article on ARG work From: "Dan'l Miller" Injection-Date: Mon, 09 Apr 2018 13:40:49 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Received-Bytes: 3782 X-Received-Body-CRC: 2885188279 Xref: reader02.eternal-september.org comp.lang.ada:51411 Date: 2018-04-09T06:40:49-07:00 List-Id: On Monday, April 9, 2018 at 2:43:46 AM UTC-5, Dmitry A. Kazakov wrote: > On 09/04/2018 05:50, Dan'l Miller wrote: >=20 > > I am saying that you are 100% incorrect that only the presence or only = the absence of the @-code will be compiled in the most-exemplary implementa= tion, leaving the other uncompiled variant to bit-rot uncompiled for extend= ed periods of time. >=20 > I didn't say that. Oh yes you did by examples, where you (and even enlisting the late Ichbiah = at one point) give examples of bit-rot where some unwise programmer of @-co= de left a presence/absence branch of the @-code uncompilable henceforth. = Your examples were clearly making the case that Mr. Unwise Programmer was g= oing to stink up the codebase with @-code that was compiled only with @-cod= e present that would break in would-be builds where @-code was absent that = Mr. Unwise Programmer cavalierly failed to test-build, but that the next be= leaguered programmer would need to rectify upon building with @-code absent= . Your entire premise was based on the mistaken claim that the build-time = would not build both presence and absence of the @-code in one shot to show= Mr. Unwise Programmer the error of his ways right then and there upfront i= n his face. Let us look at 2 of those examples: Dmitry wrote on 08 April 2018: > More complicated rules are required for declarations, e.g. that=20 > conditionally declared entities would not be visible outside conditional= =20 > code:=20 > > declare=20 > @ X : Integer;=20 > Y : Integer;=20 > begin=20 > Y :=3D X; -- This is illegal=20 > @ Y :=3D X; -- This is OK=20 > end;=20 > > or=20 > > @ with Text_IO;=20 > use Text_IO; -- No, that does not work=20