[35] in Athena_Backup_System
Re: Coding Style Guide
daemon@ATHENA.MIT.EDU (Jonathon Weiss)
Wed Oct 19 14:23:52 1994
To: tjm@MIT.EDU (Tim McGovern)
Cc: athena-backup@MIT.EDU
In-Reply-To: Your message of "Fri, 14 Oct 1994 12:39:06 EDT."
<aac42a9b0002100496de@[18.177.0.17]>
Date: Wed, 19 Oct 1994 14:23:21 EDT
From: Jonathon Weiss <jweiss@MIT.EDU>
>> With the exception of the _long_ section of options, which I think we
>> should put in an appendix, I'd say we should simply adopt the GNU guide
>> verbatim, with the following advisory when we're coding ABS:
I'm not sure this event is really relevant to ABS, but might be, and
might be relevant to other DCNS projects, an appendix is probably
reasonable.
I think we can strike the "Referring to Propriatery Programs" and
"Accepting Contributions" sections, but I'm not sure.
I think the makefile section could use some work, especially the
required targets and "Variables for Installation Directories" Maybe we
can get useful comments on these from rel-eng or dcns-dev.
The only other major concern I had is about the configuration. Do we
want to follow the GNU spec's here or stay with imake? This might
bear a fw minutes of discussion on Thursday.
>> * if there's something that simply is irrelevant to MIT,
>> we can ignore it
>> * if there's something that REALLY runs against normal
>> MIT or DCNS-dev standards ;-), then we report it to the
>> rel-eng folks, and use the local convention instead...
>> * if there's something that isn't the way it has SOMETIMES
>> been done in the past, then we use the GNU style.
With the exception of my above comments, this seems reasonable.
Jonathon
