HENSA RCS --------- - No keywords in the executables (ident gives no result) - No sources - No documentation whatsoever - Version number not indicated (-V does not work) - Default author is set to root - Diff tool is called as 'diff': conflict with Acorn diff - File names in RCS files are RiscOS-style. - File types are maintained by setting the type of the RCS file to the type of the initial workfile. - ident goes into loop if file not found - The executables are dated 29 Jul 1990; version can not be later than RCS v5.0 Main problems with v5.0: . The $ in filenames will be interpreted as the end of a keyword. This is solved by preventing the $ from appearing in a keyword. -- programs refuse file parameters which contain $ -- source and header keywords do not expand to the full pathname . Directory names are not recognised as extensions, and as a result the prefix for the Log lines will be incorrect. RCS for RiscOS v5.7.1.2 ----------------------- - RCS itself is maintained under RCS. The executables contain Id strings. - Modified sources can be found on the webpages - Documentation about how this port differs from the original is supplied - -V options gives the version number of the programs (5.7.1.2) - There is no default author. User is forced to set the name, preferably to a value that makes sense. - The diff tool is called gdiff to prevent conflict with Acorn DDE diff. - File names in RCS files are Unix style - File types are maintained by keeping a special 'type' field in the RCS file - ident reports error if file not found. - Recognises directory names as file extensions. E.g. "hop.c.banana" -> hop/banana.c -- Log comment prefix is automatically set -- requires RCS dir to be one level up for those files E.g. RCS file for hop.c.banana is hop.RCS.c.banana -- Also allows "banana" as parameter. Rcs file will be RCS.banana - This can be disabled by setting UnixFS$sfix to empty string (*set UnixFS$sfix "") -- RCS dir will be in same directory as the workfile I.e. RCS file for hop.c.banana is hop.c.RCS.banana -- Still uses the correct Log comment prefix. The NEWS documentation file tells us that the 'comment' field in the RCS file is now obsolete. The system now uses the string before the '$Log' to prefix the following log text entries. -- (Does not set Log 'comment' field automatically in the RCS file. This is not a problem, as this field has become obsolete in v5.7) - The Header and Source keywords are expanded to the full pathname, - An effort has been made to reduce the occurences of $. If a parameter is passed which contains a $, it will be removed when possible. ADFS::Csite.$.C.Tools.c.main will be reduced to ADFS::Csite.C.Tools.c.main This reduction does not happen when the program uses the Current User Directory to give the full path name of a file. $Id: Hensa.txt 1.1 1999/02/01 21:12:26 erikgrnh Exp $