Path: utzoo!utgpu!water!watmath!clyde!att-cb!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!pasteur!ucbvax!decwrl!labrea!sri-unix!quintus!ok
From: ok@quintus.UUCP (Richard A. O'Keefe)
Newsgroups: comp.lang.misc
Subject: Re: Loops
Summary: SETL
Message-ID: <885@cresswell.quintus.UUCP>
Date: 17 Apr 88 03:25:52 GMT
References: <YWK3hUy00VA88IO0UA@andrew.c <557@tuck.nott-cs.UUCP> <3041@enea.se>
Organization: Quintus Computer Systems, Mountain View, CA
Lines: 20

In article <3041@enea.se>, sommar@enea.se (Erland Sommarskog) writes:
: Dr A. N. Walker (anw@nott-cs.UUCP) writes:
: >Joe Keane (jk3k+@andrew.cmu.edu) writes:
: >>While i'm at childish flaming, i might as well say that i _really_ hate `fi',
: >>`rof', `esac', and `elihw'.  Can anyone say they're a good idea and keep a
: >>straight face?
: >	Yes.  "They're a good idea."  :-|
[I can say that too.  "]" goes with "[", so why _not_ "fi" with "fi"?]
: Ada has "end if", "end loop", "end case" and "end <name>". 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

SETL used to end everything with 'end', but you could supply some number of
tokens after it, and the compiler would check that they exactly matched the
beginning.  E.g.
	if i < j ..... end [if [i [< [j ...]]]]
I forget what the limit was, something like 3 tokens.