Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!lavaca.uh.edu!uhnix1!moray!urchin!f1505.n106.z1.fidonet.org!Dennis.Schmitz
From: Dennis.Schmitz@f1505.n106.z1.fidonet.org (Dennis Schmitz)
Newsgroups: comp.lang.c
Subject: Re: problems/risks due to programming language
Message-ID: <15473.25EEA18D@urchin.fidonet.org>
Date: 28 Feb 90 20:37:18 GMT
Sender: ufgate@urchin.fidonet.org (newsout1.26)
Organization: FidoNet node 1:106/1505 - Dennis' NotePad, Houston TX
Lines: 23

In an article of <23 Feb 90 03:17:30 GMT>, ok@goanna.oz.au (Richard O'keefe) writes:

 RO>and exiting from a loop.  I've lost count of the number of times I have
 RO>had to add a label, use a 'return', or restructure my program simply
 RO>because the place where I wanted to put a loop 'break' was inside a
 RO>switch.  The real pity of it is that BCPL used two different keywords

From 'Microsoft C Language Reference' p.152,
=============
6.2 the break statement

break;

* execution

The break statement terminates the execution of the smallest enclosing do, 
for, switch, or while statement in chich it appears....
=============

So, why would you have to restructure your program?

Later,
dEN