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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,f66d11aeda114c52 X-Google-Attributes: gid103376,public From: mheaney@ni.net (Matthew Heaney) Subject: Re: Building blocks (Was: Design By Contract) Date: 1997/09/30 Message-ID: #1/1 X-Deja-AN: 276909099 References: <342A0AC6.2F2F@dynamite.com.au> <199709251320.PAA03585@basement.replay.com> <34316EC3.5B62@dynamite.com.au> <343149D9.6A30@pseserv3.fw.hac.com> Organization: Estormza Software Newsgroups: comp.lang.ada Date: 1997-09-30T00:00:00+00:00 List-Id: In article <343149D9.6A30@pseserv3.fw.hac.com>, "W. Wesley Groleau x4923" wrote: >Unfortunately, there are those who feel that not identifying the >loop termination at the beginning of the loop confuses the reader. >These folk are supported by a non-thoughtful reading of Ada Quality >and Style. Sometimes I think this book needs to be put out to pasture. >The "guidelines" (we all know that's another word for >"rules," right?) say to only exit from a plain loop, never from >a 'while' or 'for' So folks go through wierd contortions to avoid >"exit." But the accompanying explanation clearly says that >_readability_ is the criteria for choosing a loop construct. Well stated; thank you for pointing that out. The reason for any rule...um...I mean guideline is to promote understandability and ensure correctness. How often programmers forget that in their slavish adherence to a style guide! -------------------------------------------------------------------- Matthew Heaney Software Development Consultant (818) 985-1271