LIKE ANYTHING ELSE THAT'S FREE, THESE COMMAND PROCEDURES ARE PROVIDED AS IS AND COME WITH NO WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED. IN NO EVENT WILL ATMEL CORPORATION OR NELSON INGERSOLL BE LIABLE FOR ANY DAMAGES RESULTING FROM THE USE OF THIS SOFTWARE. RCS Wildcards The command procedures in this release are designed to work with the RCS (v4.3) software ported to VMS by Richard T. Gregory and found on the VAX SIG Spring 1992 tape. They provide wildcard capability for CI, CO, RCSCLEAN, RCSDIFF, and RLOG. See RCS_SETUP.COM for my, not the only, way of using them. I am in the middle of a software project, and don't really have the time to spend working on inoculating these programs with the code in CF_VMS.C as suggested by Richard T. Gregory. (In fact I probably shouldn't be working on RCS at all... but damn it, I want code control!) Anyway, after only a few hours of perusing the code, I am concerned about breaking some of the functions in CO and CI. CF_VMS works, by the way, as can be seen in the play-program GLOP.C. > Note: Last minute addition... > > Richard Gregory has advised me that there is a "more portable" version of > RCS now on prep.ai.mit.edu. With any luck I'll get a chance to pick it up > and port it to VMS. In the meantime, these command procedures may help you > use Rich Gregory's VMS port of RCS version 4.3. ---------------------------------------- Some Comments About RCS v4.3 ---------------------------------------- The RCS programs expect that file specifications follow the parameter list. This 'expectation' is preserved in these command procedures. If you put parameters and file specifications in the 'wrong' order on the command line the RCS programs may not behave as expected. While working on this code I discovered that RCSCLEAN uses the -p qualifier and output redirection. This complicated my work. I decided that the DCL code shouldn't be onerously complicated since not everyone has the pleasure as I do, of having two VAX 4000-600's at their site. The VAX 4000-600 helps the somewhat piggy RCS processes proceed quickly. Anyway, I tried to keep the DCL code simple. Therefore, wildcards are not allowed with output redirection. Given the nature of programming, (or is it just me?), it is quite possible that a wildcard file specification will result in so many matching filenames that the DCL command line limit of 255 characters would not hold them all. (Note: I do not know what the command line limitation of UNIX, et. al., is but I assume that it is greater than 255.) To prevent this limitation from causing run-time errors I designed the DCL code to build more than one file list, as necessitated by wildcarding; and subsequently run the RCS program, e.g. CO, against each list separately. Too help avoid the combined length of the file list, parameter list, and program command from exceeding 255 characters, each file list is limited to about 132 characters. Things could still go wrong, but the likelihood is much smaller. So far, I haven't had any problems in that arena. Files you should find in this submission: AAAREADME.TXT ! This file. CIWILD.COM ! Wildcard for CI. Aliased as CI in RCS_SETUP. COWILD.COM ! Wildcard for CO. Aliased as CO in RCS_SETUP. RLOGWILD.COM ! Wildcard for RLOG. Aliased as RL*og in RCS_SETUP. RDIFFWILD.COM ! Wildcard for RCSDIFF. Aliased as RD*iff in RCS_SETUP. RCLEANWILD.COM ! Wildcard for RCSCLEAN. Aliased as RC*lean in RCS_SETUP. RCS_SETUP.COM ! RCS setup command procedure. GLOP.C ! VAXC program to test CF_VMS.C in RCS release. I hope that these procedures will be of use. If you find any problems, please let me know. All of this submission may be freely distributed. - Nelson ... ============================================================================ Nelson E. Ingersoll >< Work: (719) 540-1263 ATMEL Corporation <> INTERNET: nei@atmel.com MS 10165 >< CompuServe: 73230,2116 1150 E. Cheyenne Mountain Blvd. <> Give the very best you have! Colorado Springs, CO 80906 >< Give yourself! ============================================================================