My workplace is an xemacs shop, so we use emacs lisp modes to deal with file headers. This is the generic perl header:

#!/zack/usr/bin/perl 
#
# File:           ipchains.pl 
#
# Summary:        
#
# Author:         Jon Schatz
# E-Mail:         my@email.goes.here
# Org:            foobar.com
#
# Orig-Date:      17-Oct-00 at 16:33:56
# Last-Mod:       29-Nov-00 at 14:34:55 by jschatz
#
# Description:    
#
# $Source: /zdevel/cvs/tools/ipchains/ipchains.pl,v $
# $Date: 2000/11/29 22:35:51 $
# $Revision: 1.7 $
# $Author: jschatz $
# $State: Exp $
# $Locker:  $
[download]

The cool thing about this is that the file header is generated by emacs lisp from CVS info. So as soon as something's been commited to cvs, all the info is automagically written. There's also a disclaimer that gets added to code before it goes production ("This is unpublished proprietary code blah blah blah"), but that's nowhere near as cool as making xemacs generate these headers on the fly.

Update: I'll be happy to post up the lisp code to do this for anyone interested.

Update 2: Judgment Day: I'm actually going to write an xemacs review for the reviews section, so I'll just put all of the pertinent code there.

BlueLines

Disclaimer: This post may contain inaccurate information, be habit forming, cause atomic warfare between peaceful countries, speed up male pattern baldness, interfere with your cable reception, exile you from certain third world countries, ruin your marriage, and generally spoil your day. No batteries included, no strings attached, your mileage may vary.