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: fac41,9a0ff0bffdf63657 X-Google-Attributes: gidfac41,public X-Google-Thread: 103376,4b06f8f15f01a568 X-Google-Attributes: gid103376,public X-Google-Thread: f43e6,9a0ff0bffdf63657 X-Google-Attributes: gidf43e6,public X-Google-Thread: 1108a1,9a0ff0bffdf63657 X-Google-Attributes: gid1108a1,public From: Richard Melvin Subject: Re: Software landmines (loops) Date: 1998/09/04 Message-ID: <2QVyPDAWkD81Ew70@radm.demon.co.uk>#1/1 X-Deja-AN: 388201749 Distribution: world X-NNTP-Posting-Host: radm.demon.co.uk:194.222.155.111 References: <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> <904556531.666222@miso.it.uq.edu.au> <35EAEC47.164424A7@s054.aone.net.au> <35EFD468.BDD7CB0A@irisa.fr> X-Complaints-To: abuse@demon.net X-Trace: news.demon.co.uk 905017125 nnrp-04:21066 NO-IDENT radm.demon.co.uk:194.222.155.111 Organization: n/a MIME-Version: 1.0 Newsgroups: comp.lang.eiffel,comp.object,comp.software-eng,comp.lang.ada Date: 1998-09-04T00:00:00+00:00 List-Id: In article <35EFD468.BDD7CB0A@irisa.fr>, Jean-Marc Jezequel writes > > Result := l.first /= r.first > from l.start; r.start > invariant equal_so_far: --foreach i such as 0 -- r.item(i) = l.item(i) > variant l.count-l.current_index+1 > until not Result or l.off --r.off omitted since l.off=>r.off > loop > Result := l.item /= r.item > l.forth; r.forth > end Nice proof. Unfortunately your code contains at least one, and arguably two, bugs: - will throw an exception or return wrong result on unequal length lists. - will interfere with iteration over lists in the calling function (unless the language you are using passes lists by value, not identity). I've got a theory as to the people writing strict single/entry single code are having such a hard time with this (defect rate > 20%): - iteration through a list is actually quite hard, through two lists multiply so - there are quite a lot of opportunities for error. Of course, it doesn't seem that hard to most people, as they have memorised the correct way to loop through a list, given their language and library. - With tree structured code, you can use this memorised pattern of iteration every time, and put the custom code within the loop body, including early exit. - with strict structured code, you can't do this, as you have to adjust the loop condition, at least introducing new terms, and possibly adjusting existing ones. Anyway, it's just a theory - no doubt someone will now post a batch of tree-structured code with bugs. -- Richard Melvin