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 10.107.154.132 with SMTP id c126mr15311848ioe.7.1523146444424; Sat, 07 Apr 2018 17:14:04 -0700 (PDT) X-Received: by 2002:a9d:5220:: with SMTP id e32-v6mr1770795oth.3.1523146444336; Sat, 07 Apr 2018 17:14:04 -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!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!k65-v6no1073859ita.0!news-out.google.com!u64-v6ni1683itb.0!nntp.google.com!u184-v6no1085239ita.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Sat, 7 Apr 2018 17:14:04 -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> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <59f9ab6d-d6ba-45ff-a6f0-c5699983d9e8@googlegroups.com> Subject: Re: Interesting article on ARG work From: "Dan'l Miller" Injection-Date: Sun, 08 Apr 2018 00:14:04 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Received-Bytes: 3879 X-Received-Body-CRC: 380489673 Xref: reader02.eternal-september.org comp.lang.ada:51393 Date: 2018-04-07T17:14:04-07:00 List-Id: On Saturday, April 7, 2018 at 11:00:02 AM UTC-5, Dmitry A. Kazakov wrote: > On 2018-04-07 17:27, Dan'l Miller wrote: > > On Saturday, April 7, 2018 at 5:11:35 AM UTC-5, Dmitry A. Kazakov wrote= : > >> On 2018-04-07 04:25, Randy Brukardt wrote: > >> > >>> The biggest problem with a lexical solution (and the reason that Ichb= iah > >>> hated them) is that it's trivial to accidentally create a program tha= t is > >>> only legal in one mode or the other. One has to continually compile > >>> everything in each possible mode to ensure that there aren't silly sy= ntax > >>> errors involved. A common mistake that I make all of the time is: > >>> > >>> if Foo then > >>> Bar; > >>> else > >>> @ Internal_Error; > >>> end if; > >>> > >>> With the conditional compilation off, the "Internal_Error" is comment= ed out > >>> and the above isn't syntactically legal. > >> > >> Yes, this is important but I think this could be resolved, e.g. by > >> compiling conditionals into corresponding null-effect constructs. > >=20 > > Yeah, right. This is an artificially contrived =E2=80=9Cproblem=E2=80= =9D that is in fact not extant in reality. Simply put the @ symbols in fro= nt of the =E2=80=A2entire=E2=80=A2 construct to elide: the entire else bra= nch. > >=20 > > if Foo then > > Bar; > > @ else > > @ Internal_Error; > > endif; > >=20 >=20 > "@ else" > "@ Internal_Error;" >=20 > Is not a valid sequence of statements. That is a non sequitur, Dmitry.=20 if Foo then=20 Bar;=20 @ else=20 @ Internal_Error;=20 endif; produces either this legal Ada if-else statement, where =E2=90=A0 is the AS= CII/ISO646 space character: if Foo then=20 Bar;=20 =E2=90=A0=E2=90=A0 else=20 =E2=90=A0=E2=90=A0 Internal_Error;=20 endif; or this legal Ada if statement: if Foo then=20 Bar;=20 -- else=20 -- Internal_Error;=20 endif; Compare & contrast, and then you will understand what Randy was saying.