Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!mcnc!gatech!hao!oddjob!gargoyle!ihnp4!homxb!mtuxo!mtune!mtx5c!mtx5d!mtx5a!mat From: mat@mtx5a.COM (m.terribile) Newsgroups: comp.lang.c Subject: Re: Re: Writing readable code Message-ID: <1874@mtx5a.COM> Date: Fri, 10-Jul-87 18:16:14 EDT Article-I.D.: mtx5a.1874 Posted: Fri Jul 10 18:16:14 1987 Date-Received: Sun, 12-Jul-87 13:54:05 EDT References: <1158@copper.TEK.COM> <6858@auspyr.UUCP> <17171@cca.CCA.COM> <221@amanue.UUCP> <1221@ius2.cs.cmu.edu> Organization: AT&T Information Systems, Middletown, NJ 07748-4801. Lines: 28 > "the alternative"! Come on there are a thousand and one ways to code > the semantics of the above loop. For example : > > c = getchar(); > while (c != EOF) > { > . > . > . > c = getchar(); > } > > Look, no assignments in the conditionals, no hidden gotos (break). > For the people that argue the first form is bad, this would > probably be the approach they would take. C'mon! This is everything that is wrong with Pascal. The data for the first pass through the loop are gathered by operation X in location A. The data for the second pass of the loop are gathered by identical operation X in widely separated location B. Give us a break, fer pitsaeks! -- from Mole End Mark Terribile (scrape .. dig ) mtx5b!mat (Please mail to mtx5b!mat, NOT mtx5a! mat, or to mtx5a!mtx5b!mat) (mtx5b!mole-end!mat will also reach me) ,.. .,, ,,, ..,***_*.