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,4b06f8f15f01a568 X-Google-Attributes: gid103376,public From: Richard D Riehle Subject: Re: Software landmines (loops) Date: 1998/10/03 Message-ID: <6v5sst$e22@sjx-ixn5.ix.netcom.com>#1/1 X-Deja-AN: 397418828 References: <6qfhri$gs7$1@nnrp1.dejanews.com> <35cb8058.645630787@news.ne.mediaone.net> <902934874.2099.0.nnrp-10.c246a717@news.demon.co.uk> <6r1glm$bvh$1@nnrp1.dejanews.com> <6r9f8h$jtm$1@nnrp1.dejanews.com> <6renh8$ga7$1@nnrp1.dejanews.com> <6rf59b$2ud$1@nnrp1.dejanews.com> <6rfra4$rul$1@nnrp1.dejanews.com> <35DBDD24.D003404D@calfp.co.uk> <6sbuod$fra$1@hirame.wwa.com> <35f51e53.48044143@news.erols.com> <6sdiav$e0g$1@hirame.wwa.com> <6sfcft$70p$1@hirame.wwa.com> <1dg8p3r.vfredh1aou58iN@n207167116191.inetworld.net> <6v2nr9$t8l$1@hirame.wwa.com> <6v39i0$fte$1@winter.news.erols.com> <6v4d5l$blb$1@hirame.wwa.com> Organization: ICGNetcom X-NETCOM-Date: Sat Oct 03 12:11:25 PM PDT 1998 Newsgroups: comp.lang.ada Date: 1998-10-03T12:11:25-07:00 List-Id: In article <6v4d5l$blb$1@hirame.wwa.com>, "Robert C. Martin" wrote: in response to a note by John I Moore, Jr. about the do-while-do loop suggested by Harlan Mills, > >Yes, Mills did make this definition. However, I am referring to the work of >Dijkstra in the late 60's and early 70's. Dijkstra was very clear about the >notion of single entry and single exit within the body of a loop. I believe >that Mills'do-while-do loop is an unauthorized addition to Dijkstra's work. Is every pronouncement by Dijkstra the equivalent of Holy writ? Software is a fledgling discipline even today. It was certainly an immature practice in the 1960's. I seem to recall that Albert Einstein once said that we should try to make everything as simple as possible but not simpler. The notion of "single-entry/single-exit" is obsolete. It has been for a long time. Instead, rational programmers understand the need for control structures that are readable, understandable, and maintainable. This requires them to make the code as simple as possible "but not simpler." Single-entry/single-exit has the disadvantage of sometimes making the code not only as simple as possible, but also simpler. Perhaps we should also disallow discontinuous mathematical functions. Richard Riehle richard@adaworks.com http://www.adaworks.com