Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84 (Fortune 01.1b1); site graffiti.UUCP Path: utzoo!linus!philabs!cmcl2!seismo!ut-sally!ut-ngp!shell!graffiti!peter From: peter@graffiti.UUCP (Peter da Silva) Newsgroups: net.lang.c Subject: Re: "break" statements Message-ID: <402@graffiti.UUCP> Date: Sun, 3-Nov-85 23:01:35 EST Article-I.D.: graffiti.402 Posted: Sun Nov 3 23:01:35 1985 Date-Received: Tue, 5-Nov-85 06:38:45 EST References: <678@ucsfcgl.UUCP> <2600026@ccvaxa> <2746@brl-tgr.ARPA> Organization: The Power Elite, Houston, TX Lines: 17 > In theory, he should. The objection to break and return > from the middle of a block is that there are then multiple > exits from the block. This makes it more difficult to > establish clean termination conditions and loop invariants > for verifying the correctness of the code. Of course, few > C programmers worry about this! :-) Generally because it's not practical to prove code correct in large scale applications. In fact it's hard to apply many computer science techniques in large scale applications. This is extremely unfortunate, but until CS people start using real-world problems as the basis of their theories it will remain true. -- Name: Peter da Silva Graphic: `-_-' UUCP: ...!shell!{graffiti,baylor}!peter IAEF: ...!kitty!baylor!peter