home *** CD-ROM | disk | FTP | other *** search
- From: daves@hpopd.pwd.hp.com (Dave Straker)
- Date: Mon, 14 Dec 1992 17:43:44 GMT
- Subject: Re: C Code Layout
- Message-ID: <-191179986@hpopd.pwd.hp.com>
- Organization: Hewlett-Packard, CCSY Messaging Centre, UK.
- Path: sparky!uunet!spool.mu.edu!sdd.hp.com!hpscit.sc.hp.com!hplextra!otter.hpl.hp.com!hpopd!daves
- Newsgroups: comp.software-eng
- References: <1992Dec11.020200.944@seq.uncwil.edu>
- Lines: 30
-
- > >
- > >On the subject of C CODE layout.
- > >I require my students to use the following format.
- > ^^^^^^^ ^^^^^^^^ ^^^^^^^^^^^^^^^^
- >
- > Why in the world would you REQUIRE students to use a particular
- > coding style? Coding style is one of the things that makes each
- > programmer unique and lends some "art" to this thing we call
- > programming!
-
- This highlights an interesting teaching dilemma. Do you enforce
- standards or allow individual style? Enforcing standards teaches
- something of the 'real world' where you may have to use standards
- that you don't 100% approve of. It also meets the objective of
- easing communications about programs between lecturer and student
- (and maybe even student and student). On the other hand, there
- is no 'right' style and it may be wrong to 'lock' students into
- a single style where they may later be required to use other styles.
-
- On balance, I'd probably do a bit of both. I'd also get students
- to mark one another's work for both, thus saving a bit of lecturer's
- effort whilst simultaneously letting them find out the value of
- using a style with which other people are familiar.
-
-
- Dave Straker
-
- plug:
- (Author of 'C Style: Standards and Guidelines' Pub. Prentice Hall, 1992)
-
-