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=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,99e73f65ea2533b9 X-Google-Attributes: gid103376,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news4.google.com!feeder1-2.proxad.net!proxad.net!feeder2-2.proxad.net!newsfeed.arcor.de!newsspool3.arcor-online.net!news.arcor.de.POSTED!not-for-mail Date: Tue, 02 Sep 2008 19:32:43 +0200 From: Georg Bauhaus User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707) MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: and then... (a curiosity) References: <18b41828-bda4-4484-8884-ad62ce1c831d@f36g2000hsa.googlegroups.com> <57qdnfULQ9tzKCHVnZ2dnUVZ_tHinZ2d@comcast.com> <48bd0003$1@news.post.ch> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-ID: <48bd78bc$0$7520$9b4e6d93@newsspool1.arcor-online.net> Organization: Arcor NNTP-Posting-Date: 02 Sep 2008 19:32:44 CEST NNTP-Posting-Host: 7a9b3a49.newsspool1.arcor-online.net X-Trace: DXC=e=7JhNZ?LV8LNKYb?b>076ic==]BZ:af>4Fo<]lROoR1<`=YMgDjhg2hXZIWVe1=P:Lh>_cHTX3j=lak>Q\509O5 X-Complaints-To: usenet-abuse@arcor.de Xref: g2news1.google.com comp.lang.ada:1875 Date: 2008-09-02T19:32:44+02:00 List-Id: Ludovic Brenta schrieb: >> But do you really dispute that following the mathematical conventions >> as much as possible would improve readability? > > Of course not. That's wgy "and" should have its mathematical meaning - > i.e it should not impose an order of evaluation and it should not > avoid evaluating its operands. That's what "and then" is for. There is no order, but still the trouble is that mathematics is not usually about evaluation at all. The process of evaluating is not explicitly present in the mathematical meaning of "and". It does not build on "process" or "procedure". * Another issue with "and then" short-circuits apparears in some "elsif"s: if This_Thing and then Another_Thing then elsif This_Thing and then Yet_Another_Thing then ... more of the same ... else -- this catches, errhhm, how many of which of -- the alternatives and when? end if Nest instead and an "unambiguous if-then-else statement" removes the need of low-level source code optimization such as too many short-circuits. Makes your fuses blow :) :) -- Georg Bauhaus Y A Time Drain http://www.9toX.de