Path: utzoo!mnetor!uunet!ncc!alberta!att-ih!ihnp4!ihlpf!nevin1 From: nevin1@ihlpf.ATT.COM (00704a-Liber) Newsgroups: comp.lang.misc Subject: Re: Loops Message-ID: <4469@ihlpf.ATT.COM> Date: 19 Apr 88 00:01:53 GMT References: <3041@enea.se> Reply-To: nevin1@ihlpf.UUCP (00704a-Liber,N.J.) Organization: AT&T Bell Laboratories - Naperville, Illinois Lines: 29 In article <3041@enea.se> sommar@enea.UUCP(Erland Sommarskog) writes: |The bad point with words like "esac" is that you have to read them twice, |at least, to see what's going on. After the first couple of times, I had this one memorized. |The sole advantage over "end case" is that you save some keys to type. |[...] |"End case" is clearer. It also have the advantage that you only have to |read "end" if you're just taking a quick glance; The fact that it is the |end of a case-statement may be irrelevant at the moment. 'End case' usually takes me longer to read, since I usually read it as two separate English words vs. 'esac', which I consider to be a simply memorized end of case. |Note also that "end if" (or "fi" or whatever") helps you little when |you have many nested if-statements. You're just as bad out as with |only "end", unless you add a comments like: | end if; -- test A | end if; -- test B Oh, no!! You and I agree on something, again!! :-) -- _ __ NEVIN J. LIBER ..!ihnp4!ihlpf!nevin1 (312) 510-6194 ' ) ) "The secret compartment of my ring I fill / / _ , __o ____ with an Underdog super-energy pill." / (_