Xref: utzoo comp.lang.c:15079 comp.unix.wizards:13682
Path: utzoo!attcan!uunet!husc6!rutgers!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn )
Newsgroups: comp.lang.c,comp.unix.wizards
Subject: Re: Standards
Message-ID: <9225@smoke.BRL.MIL>
Date: 24 Dec 88 19:56:35 GMT
References: <3229@ingr.UUCP> <253@athertn.Atherton.COM> <9166@smoke.BRL.MIL> <439@maxim.ERBE.SE>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 13

In article <439@maxim.ERBE.SE> prc@maxim.ERBE.SE (Robert Claeson) writes:
-In article <9166@smoke.BRL.MIL>, gwyn@smoke.BRL.MIL (Doug Gwyn ) writes:
-> I've read quite a few DoD coding standards, data format standards,
-> program documentation requirements, etc.  They're generally pretty
-> horrible, requiring products that I personally would consider
-> inexcusably poor workmanship!
-So what style do *you* use when you write code, Doug?

Whatever's appropriate for the language, etc., keeping in mind the
needs of future maintainers (including myself after a few months).

One thing I do NOT do is provide punched-card decks and flowcharts.
(DFDs and FSA diagrams, yes, flowcharts, no).