From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 109fba,d95b511473b3a931
X-Google-Attributes: gid109fba,public
X-Google-Thread: 103376,d95b511473b3a931
X-Google-Attributes: gid103376,public
X-Google-Thread: 1014db,d95b511473b3a931
X-Google-Attributes: gid1014db,public
From: Dan Evens <evensd@nts.ohn.hydro.on.ca>
Subject: Re: Language Choice and Coding style
Date: 1996/07/04
Message-ID: <31DC064B.289@nts.ohn.hydro.on.ca>#1/1
X-Deja-AN: 163702371
references: <nh3f3pppsl.fsf@paralysys> <4quk22$78@krusty.irvine.com>
 <4r059t$2at0@info4.rus.uni-stuttgart.de> <Dtprq5.4Dr@world.std.com>
 <4r3bp1$cea@Starbase.NeoSoft.COM> <dewar.836067024@schonberg>
content-type: text/plain; charset=us-ascii
organization: Ontario Hydro, Canada
mime-version: 1.0
newsgroups: comp.lang.ada,comp.lang.c,comp.lang.c++
x-mailer: Mozilla 2.01 (Win16; I)
Date: 1996-07-04T00:00:00+00:00
List-Id: <comp.lang.ada>


Robert Dewar wrote:
> 
> Samuel says
> 
> "Anyway, for this particular small area -- code formatting -- the best
> approach is to use a formatting editor, so everybody can set up his
> *own* preferences and see the code the way *he* finds most readable.
> (Or she.)"
> 
> I strongly disagree. In theory this sounds OK, but style covers much more
> than simple rules that can be messed around with by a formatting editor.
> If a team is not willing to agree on unimportant little things, but insists
> on going their own individual way, I think you have little hope of
> achieving a high degree of coding style consistency, something I think
> is vital for the success of software projects with more than one person
> involved.

I strongly agree with Robert here.  Coding style is a very long book,
and formatting is one chapter. And not a particularly long chapter.
Things like naming conventions, loop initializations, number of lines
in code blocks, number of args to routines, etc., are all important
to coding style also. For projects with hundreds of subroutines and
many tens of thousands of lines of code, some of these things can make
just HUGE differences to things like the app being maintainable.

-- 
The preceding are my opinions alone and have nothing
whatever to do with my employer.  I don't even know what my
employer thinks. I'm not even real sure who the CEO is.
Dan Evens