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: a07f3367d7,11414a19b0e4a97a X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news3.google.com!feeder.news-service.com!feeder3.cambriumusenet.nl!feed.tweaknews.nl!87.79.20.105.MISMATCH!news.netcologne.de!ramfeed1.netcologne.de!newsfeed.arcor.de!newsspool1.arcor-online.net!news.arcor.de.POSTED!not-for-mail Date: Wed, 23 Jun 2010 13:17:41 +0200 From: Georg Bauhaus User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Advice on selling Ada to a C shop References: <101bf8f3-b823-45ee-9afd-40cbafb4b7a9@t26g2000prt.googlegroups.com> <6a91b770-a1e5-48bf-bd16-4e451f862b8c@d16g2000yqb.googlegroups.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-ID: <4c21ed56$0$6777$9b4e6d93@newsspool3.arcor-online.net> Organization: Arcor NNTP-Posting-Date: 23 Jun 2010 13:17:42 CEST NNTP-Posting-Host: 696f8f86.newsspool3.arcor-online.net X-Trace: DXC=5>^nc\616M64>ZLh>_cHTX3j]B^IbOCTgBJU X-Complaints-To: usenet-abuse@arcor.de Xref: g2news2.google.com comp.lang.ada:12854 Date: 2010-06-23T13:17:42+02:00 List-Id: On 23.06.10 09:40, Gautier write-only wrote: > On 23 juin, 09:17, Maciej Sobczak wrote: > >> Do you think that 'end if' at the wrong place and a misleading >> indentation would produce much better results? > > Of course not, but the point is that > - the "end if" was *not* at the wrong place, probably because it would > have (or had) pooped to the eye very quickly > - in the C code, two people read and re-read and did not notice > anything wrong; the bug was detected only by examining results closely > This on only ~15 lines... A frequent argument brought forth by practical programmers is that you know how to diligently use {}. Experienced programmers don't have trouble with brackets (at least not in tie sizing discussions). Bracket problem avoidance techniques are easy to learn, hence everyone can demonstrate their competence proudly and with an air of knowledge. There are more important problems in life than brackets. How often do they create trouble? Why do you employ programmers who cannot properly use brackets? Etc.