Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!topaz.rutgers.edu!ron
From: ron@topaz.rutgers.edu (Ron Natalie)
Newsgroups: comp.lang.c
Subject: Re: goto's in C: an opinion...
Message-ID: <13408@topaz.rutgers.edu>
Date: Mon, 20-Jul-87 17:56:37 EDT
Article-I.D.: topaz.13408
Posted: Mon Jul 20 17:56:37 1987
Date-Received: Wed, 22-Jul-87 01:19:55 EDT
References: <3289@bigburd.PRC.Unisys.COM> <7571@beta.UUCP> <6603@think.UUCP>
Organization: Rutgers Univ., New Brunswick, N.J.
Lines: 16
Keywords: C, goto, style

> The example everyone knows is multi-level break.  It's clearly
> structured, but C doesn't have it.

It is not clearly structured, it isn't structured at all.  It destroys
the loop structure.  See my previous message

> (It isn't even possible to use
> 'break' to get out of a singly nested loop if the body is a switch
> statment).

This is a bug in C.  "BREAK" was a bad choice, either switch should
have implicitly assume break before the next case or it should have
used a different reserve word.  Witness the difference in operation
of the word "continue" as a result.

-Ron