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.1 required=5.0 tests=BAYES_40,INVALID_DATE,
	MSGID_SHORT autolearn=no autolearn_force=no version=3.4.4
Xref: utzoo comp.software-eng:3148 comp.lang.ada:3420 comp.lang.c:26804 comp.lang.lisp:2902 comp.lang.misc:4410 comp.lang.modula2:2164 comp.lang.pascal:3211
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!mstan!amull
From: amull@Morgan.COM (Andrew P. Mullhaupt)
Newsgroups: comp.software-eng,comp.lang.ada,comp.lang.c,comp.lang.lisp,comp.lang.misc,comp.lang.modula2,comp.lang.pascal
Subject: Re: problems/risks due to programming language, stories requested
Summary: Please. Not in comp.lang.pascal
Message-ID: <775@s5.Morgan.COM>
Date: 10 Mar 90 17:50:32 GMT
References: <1004@micropen> <8218@hubcap.clemson.edu> <2596@gmu90x.gmu.edu> <672@software.software.org>
Organization: Morgan Stanley & Co. NY, NY
List-Id: <comp.lang.ada>

> or less repetitious (which is not) in a case like this:
> 
>           switch (what_to_do) {
>                     case FIVE_THINGS:
...

This stuff doesn't belong in comp.lang.pascal. It goes in comp.lang.c,
right(?). The fistfight over bill wolfe's complaints about C should
stay in comp.lang.c. If anyone wants to complain about Pascal, then
put it in here. 

BTW - fall through and the 'double duty' break keyword are
definitely examples of C flaws.  If you must, flame me, but in 
comp.lang.c, (OK?)

Later,
Andrew Mullhaupt