Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 26 Nov 2002 00:18:23 +0100
From:      Cliff Sarginson <cls@raggedclown.net>
To:        freebsd-chat@FreeBSD.ORG
Subject:   Re: Style(9) question
Message-ID:  <20021125231823.GA567@raggedclown.net>
In-Reply-To: <f17kf18j4v.kf1@localhost.localdomain>
References:  <20021122193040.GA23078@dogma.freebsd-uk.eu.org> <20021122214405.GA11011@HAL9000.homeunix.com> <8gof8g83w4.f8g@localhost.localdomain> <20021124090603.GA3172@HAL9000.homeunix.com> <20021124100846.GC51850@raggedclown.net> <f17kf18j4v.kf1@localhost.localdomain>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Nov 25, 2002 at 12:54:56PM -0800, Gary W. Swearingen wrote:
> Cliff Sarginson <cls@raggedclown.net> writes:
> 
> > [snip] This basically meant everyone ignored them (I think actually
> > that nobody read them).
> 
> More common, from my experience, is good-old-boy, wink-of-the-eye
> variable enforcement of standards, so that standards are learned and
> followed best by the persons who recieve the most frequent and severe
> sanctions for violations.  (And to a lesser degree, by those with the
> least pressure to produce working code.)  The system obviously has some
> practical merit, but it often results in a lot of unhappy programmers.
> 
> This is one reason for very strict enforcement of standards -- even
> automated systems -- so that favoritism doesn't rear it's ugly head.
> Of course, it tends to slow down and ire the most productive coders.
> 
Mmm. Well then we get to the question of what productivity means. Joe
Wizard may turn out working code very quickly, but written in his own
idiosyncratic style. 2 years later, he has burnt out and is raising
chickens from a caravan in Wales. Fred Newbie is assigned the task of
maintaining Joe's code and he goes cross-eyed in the process...so his
productivity is severely impaired. If people are writing code probably
destined for a long-life it seems to me not such a bad idea that some
kind of standard format, even a loose one, is better than none at all.

But we keep going back to the point on agreement of what is a style
generally usable by most programmers. Unless you give the powers of
Cardinal Richelieu to the program authority on this, there will always
be programmers who will not follow *any* of the guidelines. If such a
person presents a 2000 line program, written without a care for any poor
sod that is going to have to read it, but it "works", what Project
Manager will be pleased to hear that he has been told to re-format it,
an activity that may take days of begrudged work.

So enforcement is better before and during the act, it is fairly
hopeless afterwards. 


-- 
Regards
   Cliff Sarginson 
   The Netherlands

[ This mail has been checked as virus-free ]

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-chat" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021125231823.GA567>