Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site birtch.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!qantel!hplabs!sdcrdcf!trwrb!scgvaxd!felix!birtch!oleg
From: oleg@birtch.UUCP (Oleg Kiselev x258)
Newsgroups: net.lang.c
Subject: Re: C style
Message-ID: <142@birtch.UUCP>
Date: Wed, 2-Oct-85 00:15:57 EDT
Article-I.D.: birtch.142
Posted: Wed Oct  2 00:15:57 1985
Date-Received: Mon, 7-Oct-85 03:43:17 EDT
References: <1556@brl-tgr.ARPA> <3400010@ndm20>
Organization: Birtcher, Santa Ana, Ca.
Lines: 23


 Terry Poot writes in <3400010@ndm20>
> Some of us feel the same about breaks as we do about gotos. I won't use it, or
> continue either, and I won't let anyone in my shop use it. It is just a goto
> with an implicit label, and destroys the ability to determine program flow from
> the FORM of the source even more drastically, as there is no label to catch 
> your eye and alert you to the presence of the d*mned thing. The only way I will
> use a break is in a set of macros implementing a middle exit loop construct.
> We use LOOP...LOOPUNTIL...ENDLOOP. I know, adding features to a language with
> #define has problems, but at least that code is readable once you know what the
> constructs do, which is quite apparent. C should have that structure built in.
> Since it doesn't, we add it. The keywords are at the same indentation level, of
> course.
WHY??? What do you need LOOP...etc for when you have "do...while(...);" and 
"while (...) ...." ???? 
And about "break" : HOW do YOU get around "switch" statements ? or do you use
"if... then .... else if .... then ..........."? May be you even #defined that
to be IF, THEN, ELIF, FI like Bourne does? 

Go ahead, do what you feel like! But don't complain when the next time someone
refuses to *even look* at your stuff without cpp-ing it first!

														   Oleg Kiselev