[273,200] DECUS C Documentation This account was created for the purpose of documenting the librarys in [273,201]. There are command files to build documentation, and runoff header files for each of the documents in [273,201]. These command files have been generalized so that they will document any set of routines with the DECUS 'C documentation standard. MAKDOC.CMD This command file creates a manual for a specified set of routines. Format : @MAKDOC lisfil LISFIL is a file containing a list of functions to be placed in the document. The name of the file is carried through to be used as : 1. Name of document header files [lisfil]1ST.RNO [lisfil]HDR.RNO 2. Name of the created .RNO and .DOC files [lisfil].RNO [lisfil].DOC 3. Name of the Function index file output [lisfil].IND 4. The device name and uic specified in the list File spec. is used as the default for the 'C source file specification. The account you are logged into is the account that the output files are created on. This function assumes that all source files a C, perhaps someone would modify it to copy with macro source files as well [very little to change]. MAKFNLIS.CMD This command file creates A .IND file as above, without the documentation the same rules for the file name apply as above LSTNOTDOC.CMD This command file is meant to find un-documented files... It FAILED ... would someone please fix it. FNAMEPARS.CMD This command file gets a file name passed to it and strips it into it's various componants. Is called by .SETS DEFDEV "defualt device name including colon" .SETS DEFUIC "default uic including brackets" .SETS DEFEXT "default file extension including period" @FNAMEPARS/LO filename ; DEV has resolved device name ; UIC has resolved uic ; FILE has file name ; EXT has resolved file extension ; FILNAM has composite file name with resolved items BATDOC.CMD This command file creates a command file to submit to the batch to create documentation. The format is @BATDOC lisfile destin Where lisfile is the listing file to search through same as MAKDOC, and destin is the device/uic specification of where the documentation is to be put GO.CMD This command file changes the default device/uic. Format is : @GO DEV:[UIC] Brackets are not nessacerry for the uic, and the uic may be spaced apart from the device. I have since found a bug in MAKDOC.CMD : Every time GETRNO starts up, as a matter of course, it sets up headers etc for RNO. This has the effect of putting the header line for a page of documentation onto the next page, therfore putting the header line out by one page throughout the document. I havn't had time to bash this bug [ I think that I will have to put another switch into GETRNO ] so if someone thinks it's worth doing, please send me a copy. ...BRU [No not that DEC f[]utility, Bruce Cook].