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=0.7 required=5.0 tests=BAYES_00,INVALID_DATE,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!uunet!tut.cis.ohio-state.edu!ucbvax!ENUXHA.EAS.ASU.EDU!koehnema
From: koehnema@ENUXHA.EAS.ASU.EDU (Harry Koehnemann)
Newsgroups: comp.lang.ada
Subject: Re: "Ada and C++", from comp.software-eng
Message-ID: <9105091619.AA11844@enuxha.eas.asu.edu>
Date: 9 May 91 16:19:11 GMT
References: <5148@dftsrv.gsfc.nasa.gov> <1991May2.154953.4765@...!asuvax!gtephx> <1991May9.061021.1941@netcom.COM>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: koehnema@enuxha.eas.asu.edu (Harry Koehnemann)
Organization: Arizona State University
List-Id: <comp.lang.ada>

In article <1991May9.061021.1941@netcom.COM> jls@netcom.COM (Jim Showalter) writes:
>>the bug that brought down the switch which "took out the whole east
>>coast" was related to a C 'switch' statement that was missing a
>>'break'.
>
>If you leave out 'break', that's exactly what happens!

I heard (Software Engineering Notes) that the error was not a forgotten
break, but thatthe programmer was trying to exit the middle  of an if
statement by using a break (the fool he was..).  That statement (break)
does not work in that manner and it terminated the switch instead.
They didn't forget a break, they used it inappropriately.

For what its worth....