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=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,e06a5d07678a4288
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 1994-09-07 22:10:55 PST
Path: 
 nntp.gmd.de!newsserver.jvnc.net!nntpserver.pppl.gov!princeton!gw1.att.com!csn!boulder!news.coop.net!news.den.mmc.com!iplmail.orl.mmc.com!romulus23!dennison
From: dennison@romulus23.DAB.GE.COM (Ted Dennison)
Newsgroups: comp.lang.ada
Subject: Re: New Ada Emacs mode !
Date: 6 Sep 1994 13:39:22 GMT
Organization: General Electric SCSD, Daytona Beach FL
Sender: dennison@romulus23 (Ted Dennison)
Distribution: world
Message-ID: <34hrea$iil@theopolis.orl.mmc.com>
References: <33uifi$pco@lang8.cs.nyu.edu> <341rj4$bd0@theopolis.orl.mmc.com>
 <BEVAN.94Sep4132752@lemur.cs.man.ac.uk>
NNTP-Posting-Host: romulus23.orl.mmc.com
Date: 1994-09-06T13:39:22+00:00
List-Id: <comp.lang.ada>

In article <BEVAN.94Sep4132752@lemur.cs.man.ac.uk>, bevan@cs.man.ac.uk (Stephen J Bevan) writes:
|> [ I tried email but it bounced - bevan ]

I'm sorry about this one. For some reason my email address is
being incorrectly posted. I should complain to my postmaster about
this, but I'm too lazy.

I should also routinely post my real address, but again, laziness
tends to get the better of me.

|> 
|> In article <341rj4$bd0@theopolis.orl.mmc.com> dennison@romulus23.DAB.GE.COM (Ted Dennison) writes:
|>    o  -  Are you working on a more elaborate header?  I usualy need way more 
|> 	 documentation that just Author, Title, and Creation Date.
|> 
|> Just curious: why store this information in the file rather than being
|> mainly implicit in a revision control system?

Heh Heh Heh! Good question. I'll make sure to forward it to my CM and QA 
people, not that it will do any good.  

Let's just say that on (most) every project I work on, there are code 
header standards. I have never seen them require that little information.
Typical requirements are for a more detailed description, description of
all parameters, list of all possible exceptions that might be raised, and
explanation of any side efects a routine might have. File headers typicaly
require a running list of changes to the file be kept, with authors, dates,
and reason for change (even though this info is avaiable through sccs or 
any other decent revision control system).

T.E.D.
dennison@romulus.orl.mmc.com