Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!godot!harvard!seismo!brl-tgr!ron
From: ron@brl-tgr.ARPA (Ron Natalie )
Newsgroups: net.lang.c
Subject: Re: Re: using break instead of goto
Message-ID: <7358@brl-tgr.ARPA>
Date: Tue, 15-Jan-85 15:29:14 EST
Article-I.D.: brl-tgr.7358
Posted: Tue Jan 15 15:29:14 1985
Date-Received: Fri, 18-Jan-85 03:26:44 EST
References: <7210@brl-tgr.ARPA>
Organization: Ballistic Research Lab
Lines: 15
> I really think the discussion of "goto" in C is overblown.
> I just grepped through over 6,000 lines of production C code
> and found one instance of goto used as an EOF exception escape
> and 7 instances (in the same module) of gotos to a common error
> return. Not a single goto for any other purpose, including
> multi-level breaks. I would argue that this code exhibits
> why "goto" can be useful and that the "dangerous" uses of it
> can be totally avoided. Perhaps programmer education is more
> important than changing the language.
Yes, this is an indication that the reason most good programmers
place non-structured constructs in their code is to avoid code
duplication.
-Ron