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 X-Google-Thread: f43e6,9a0ff0bffdf63657 X-Google-Attributes: gidf43e6,public X-Google-Thread: fac41,9a0ff0bffdf63657 X-Google-Attributes: gidfac41,public X-Google-Thread: 1108a1,9a0ff0bffdf63657 X-Google-Attributes: gid1108a1,public From: "Robert Martin" Subject: Re: Software landmines (loops) Date: 1998/09/02 Message-ID: <6sjnlu$83l$1@hirame.wwa.com>#1/1 X-Deja-AN: 387152038 References: <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@ <904556531.666222@miso.it.uq.edu.au> <6sgror$je8$3@news.indigo.ie> <6sh3qn$9p2$1@hirame.wwa.com> <6simjo$jnh$1@hirame.wwa.com> <35eeea9b.2174586@news.erols.com> <6sjj7n$3rr$1@hirame.wwa.com> <35f055a5.1431187@news.erols.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Organization: WorldWide Access - Midwestern Internet Services - www.wwa.com Newsgroups: comp.lang.eiffel,comp.object,comp.software-eng,comp.lang.ada Date: 1998-09-02T00:00:00+00:00 List-Id: Ell wrote in message <35f055a5.1431187@news.erols.com>... >On Wed, 2 Sep 1998 08:52:36 -0500, "Robert Martin" >wrote: > >> >>Ell wrote in message <35eeea9b.2174586@news.erols.com>... >>> >>>You have not shown at all that "single entry, single exit" is a >>>general coding maxim of structured programming. > >>Well, that's your opinion. > >It's a *fact*! You are entitled to that opinion. > >>But I have cited the section of Dijkstra's book >>"Structured Programming" that talks about this; >>and have quoted the page where it is elaborated; > >That single fragment of a sentence, or at most single sentence, about >*flowcharting* in no way made the case that *coding* in the structured >paradigm should generally adhere to "single entry and single exit". The point of the citing, and the quotation, was to guide you to read it for yourself. I'm not going to reproduce two or three pages of text for your benfit. The cited section is very unambiguous in its recommendation of single-entry and single-exit. The section was not about *flowcharting*, rather it used four different generic flowcharts (all with single entry and single exit) to describe the fundemental building blocks of structured programming. Elliott, you really ought to read the book. I've given you enough pointers. Do your homework. Robert C. Martin | Design Consulting | Training courses offered: Object Mentor | rmartin@oma.com | Object Oriented Design 14619 N Somerset Cr | Tel: (800) 338-6716 | C++ Green Oaks IL 60048 | Fax: (847) 918-1023 | http://www.oma.com "One of the great commandments of science is: 'Mistrust arguments from authority.'" -- Carl Sagan