Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.3 Tandy Xenix 02/17/86; site gilbbs.UUCP Path: utzoo!watmath!clyde!burl!ulysses!gamma!epsilon!zeta!sabre!petrus!bellcore!decvax!decwrl!pyramid!hplabs!qantel!ptsfa!gilbbs!mc68020 From: mc68020@gilbbs.UUCP (Tom Keller) Newsgroups: net.cse Subject: Re: working programs Message-ID: <91@gilbbs.UUCP> Date: Tue, 18-Mar-86 12:18:32 EST Article-I.D.: gilbbs.91 Posted: Tue Mar 18 12:18:32 1986 Date-Received: Fri, 21-Mar-86 04:47:16 EST References: <9431@ritcv.UUCP> <244@umcp-cs.UUCP> <2213@jhunix.UUCP> <455@ucsfcca.UUCP> Organization: Gil's Place, Santa Rosa CA Lines: 33 Dick Karpinski makes some interesting points. In essence (please correct me if my summary misrepresents what you are saying, Dick) what I understand his position to be is as follows: In as much as "real world" programs can never be fully tested, and in as much as specifications for programming assignments tend to be nebulous at best, he feels that style should be considered at least as important as whether or not a program works. He argues maintainability, in essence. Yes, Dick, I agree that programming students need to learn style. But I disagree to the extent that a program which doesn't even come close to performing the desired function, and which won't even pass through the compiler should not carry any value. Many of the programs of this nature to which we are referring are written by students who frequently are unable to explain the intended operation of the code they have produced. Style shouold certainly be considered when evaluating a programming assignment, and emphasis on style is essential. But non-functional programs (no programs which have minor problems, but totally non-functional) should not be acceptable under any circumstances. -- ==================================== Disclaimer: I hereby disclaim any and all responsibility for disclaimers. tom keller {ihnp4, dual}!ptsfa!gilbbs!mc68020 (* we may not be big, but we're small! *)