Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!rochester!rutgers!husc6!cmcl2!brl-adm!adm!DHowell.ElSegundo@Xerox.COM From: DHowell.ElSegundo@Xerox.COM Newsgroups: comp.lang.c Subject: Multiple Returns Message-ID: <8667@brl-adm.ARPA> Date: Tue, 4-Aug-87 15:12:35 EDT Article-I.D.: brl-adm.8667 Posted: Tue Aug 4 15:12:35 1987 Date-Received: Thu, 6-Aug-87 04:02:05 EDT Sender: news@brl-adm.ARPA Lines: 15 There have been several messages posted concerning code with multiple returns. I am currently going through a two page routine with a return on almost every other line, and let me tell you, it is nothing but a mess. I think that if you need to put a return in the middle of a routine, you haven't really thought out the organization of your algorithm. Whatever happened to the structured programming concept of one entry and one exit? With multiple returns, in order to figure out the conditions on a certain piece of code, I have to follow the code through, looking at every conditional return to determine whether it applies or not. I would much rather see the code in nested if statements, where I can immediately see which conditions apply to the piece of code I am concerned with. Dan