Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles; site ea.UUCP
Path: utzoo!watmath!clyde!burl!mgnetp!ihnp4!inuxc!pur-ee!uiucdcs!ea!mwm
From: mwm@ea.UUCP
Newsgroups: net.lang.c
Subject: Re: Re: Comments on book review (cstyle - (nf)
Message-ID: <5700009@ea.UUCP>
Date: Wed, 30-May-84 12:10:00 EDT
Article-I.D.: ea.5700009
Posted: Wed May 30 12:10:00 1984
Date-Received: Wed, 6-Jun-84 04:57:17 EDT
References: <3878@utzoo.UUCP>
Lines: 23
Nf-ID: #R:utzoo:-387800:ea:5700009:000:916
Nf-From: ea!mwm    May 30 11:10:00 1984

#R:utzoo:-387800:ea:5700009:000:916
ea!mwm    May 30 11:10:00 1984

/***** ea:net.lang.c / uiucdcs!liberte /  7:11 pm  May 28, 1984 */
Maybe the best solution is to find a style that does work for most people
and the teach the remaining incorrigibles how to live with it.  Most 
aspects of style hardly matter all that much and most people will go along
with whatever is choosen, if it is reasonable.  But at the same time,
it is important to allow the freedom to explore new styles that just 
might be better.  The old innovation vs. standards tradeoff.


Daniel LaLiberte          (ihnp4!uiucdcs!liberte)
U of Illinois, Urbana-Champaign, Computer Science
{moderation in all things - including moderation}
/* ---------- */

The trick, of course, is getting people to use the "standard" 
style/methodology (We switched tracks somewhere in there). Given the
horror stories seen here recently, I suspect that getting people to
*teach* a style/methodology will be the hard part.