dUFLP (dBASE User's Function Library Project) Header Notation

Below is an example of the standardized notation agreed upon by those of us
who took the time to attempt a standardized notation. This should be used in
all functions and procedures uploaded as part of the dUFLP project.

FUNCTION AllTrim && {ver 0.8}
*------------------------------------------------------------------------------
*-- Programmer..: HazMatZak
*-- Date........: 07/02/1991
*-- Notes.......: Used to remove leading and trailing blanks from
*                 a string.
*-- Written for.: dBASE IV, 1.1
*-- Rev. History: 05/23/1991 0.1 - Original version (CLW)
*                 06/18/1991 0.2 - Revision to modify for dHUNG
*                 06/19/1991 0.3 - Revised for ...
*                 06/24/1991 0.4 - Revised for ...
*                 06/25/1991 0.5 - Revised again by Ken Mayer
*                                  to give smaller header ...
*                 etc.
*-- Calls.......: None
*-- Called by...: Any
*-- Usage.......: AllTrim(<cArg>)
*-- Example.....: ? AllTrim("  Test string  ")
*-- Returns.....: String to be trimmed (i.e.:"Test string")
*-- Parameters..: cArg = String to be trimmed
*------------------------------------------------------------------------------
       
   parameters cArg

RETURN ltrim(rtrim(cArg))
*-- EoF: AllTrim

This notation, plus any comments inside a function or procedure will give
something that we can all use, and by using the header given above, it will
make it possible to create a routine either in dBASE or some other software
that can generate a library listing, giving the pertinant information. 

This information should be combined with the information in the dHUNG.TXT
(or dHUNG.ZIP) file found in the dBASE IV library, which is a modification 
to the Hungarian notation for xBase applications. 

The dBASE User's Function Library Project is aimed at creating a library of
functions and procedures that can be used "as is" by anyone, and is created
by the users of the Ashton-Tate Bulletin Board. Ashton-Tate takes no 
responsiblity for these functions/procedures. This is being done with the
permission of A-T, but not as an official action of A-T. (If there's something
wrong with a function/procedure, please leave a note in the sig /DB4_PRG,
and someone will attempt to fix the problem ASAP.)