.ap;.lm 10;.rm 80;.nhy;.nj .t Languages and Tools SIG Spring 1989 SIGtape .c;Languages and Tools SIG Spring 1989 SIGtape .i -10 1 GNU Software from the Free Software Foundation .br This area contains several programs from the Free Software Foundation, a group working on a complete replacement for Un*x which will solve performance and reliability problems with the Un*x OS and add new functionality. Included are BISON (a YACC superset), an AWK, Gnu Emacs, Gnu C, Gnu C++, and several more. The VMS binaries for a bootstrap Gnu C for VMS are included also. There are also VMS versions of BISON, GAWK, and GNU GREP. .s Please note that these utilities are primarily for GNU with VMS variants in some cases. Also, Gnu C is a BETA version. It is fairly usable nonetheless, and version 1.30 here is quite recent. .i -10 4 MDRAW, S.#Mike Dierken, Sundstrand Data Control .br A freehand drawing utility for TeX, a mouse and a VT2xx or VT3xx graphics terminal. .i -10 5 VAX BASIC Toolkit of Useful Callable Functions .br;Brian Lomasky, Teradyne, Inc. (Spring 88 session LT029) .s These routines form the beginning of a "Toolkit" of useful and frequently-used functions that VAX BASIC (and other languages) programmers may need. These include: .s .br;Numeric Conversion Functions .br;Process Info Functions .br;User Authorization File Functions .br;RMS/Directory Functions .br;Date Functions .br;Queue Functions .br;Miscellaneous Functions .i -10 8 NSWC RUNOFF, Alan L. Zirkle, Naval Surface Warfare Center .br NSWC RUNOFF, which is based on, and derived from, Bonner Lab Runoff (VAX version) from the VAX86C VAX SIG Tape. NSWC RUNOFF has been extensively updated since it was previously submitted in Spring 1988. The files for this are in subdirectory [.RNO]. See [.RNO]000README.1ST. .s NSWC RUNOFF (RNO) is an alternative to VMS RUNOFF (DSR). It has many capabilities not in DSR, including the ability to use macros and the means of easily using the features of whatever output devices are available (i.e. RNO understands escape sequences and uses them in a structured manner). .i -10 20 XEVE spelling checker, Tom Wolfe, Jet Propulsion Laboratory .br This is the VAX/VMS 5.x version of the the XEVE spelling checker. Some of the other edit functions in the 4.x version of XEVE have not been converted to 5.x and are not included in this distribution. The XEVE spelling checker includes the following: .s Three dictionaries are used to test the spelling of words. A common dictionary (standard english words), a project dictionary (acronyms, etc). and a user defined dictionary. The user defined dictionary can be created/updated while in an EVE edit session. Utilities are provided to build all three dictionaries from text files containing one word per line. The source word file for the common dictionary must be in ascending (lexical) sort order. The project and user source word files do not. .s The EVE spelling checker also has special commands that understands a little about C, DCL, FORTRAN, DCL and MACRO source code files and only checks appropriate things. For example, The "SPELL FORTRAN" command checks only comments and character constants. The special commands are currently very primitive. .s A separate (standalone) spelling checker patterned after the LBL software tools SPELL utility is also available. .i -10 25 Space Telescope Science Institute Tools Group .br The CKMAP tool scans a VMS link map for PSECT mismatches and undefined symbols and reports these accordingly. .s The Disk Report tool scans one or more directory log files creating a series of reports summarizing disk space utilization. .s The Show Merged CMS Classes tool compares all of the elements in a CMS library class (typically an SPR class) to see if they are also inserted, or ``merged'' into another class (typically a PENDING class) in that same CMS library. .s An image definition file contains the information on how to build an executable image. It is the primary input to IMGDEF, which is used to produce an options file, an MMS file to describe the LINK process, and an MMS file for building the image and its components. .s The Remote CMS tool provides an interface to CMS libraries on a different DECnet node. This lets the user issue CMS commands that access a CMS library on a different VAX without having to log onto that node. .s The DCOPY is a modified version of the VMS COPY command that deletes a file in the destination directory before it copies into it. Before it copies the file to the destination directory, it checks for the existence of the file, and if it exists already AND the revision date of the existing file is older than the revision date on the file to be copied, DCOPY deletes the file. This is useful when disk space is tight on the destination device. Stretched logicals are also supported such that only the first version of a file is copied over a stretched directory list. .s The MMSGEN tool is used to generate a compile MMS for files with the following extensions: .FOR, .EQF, .EQE, .FBL, .C, .SCN, .MSG, .MAR, .MBL, .X. It scans one or more input files creating one or more MMS files with the correct dependency list and action lines to build or compile to target object file. .s The Link Check tool verifies the existence of all input files on a link command, passing the command onto the Linker if all inputs exist. Link Check is a workaround for a bug in the Linker that causes it to go into an endless loop when processing many objects with logical searchlists when one of the objects is missing (either from the command line or an options file). .i -10 26 SDE, Memorex Telex .br SDE is a general model software development methodology that incorporates DEC/CMS and DEC/MMS. .i -10 27 REMTAB, Bob Ribokas, Teradyne, Inc. .s REMTAB is a collection of routines that were designed to ease the task of dealing with static and semi-static data definitions that are used by multiple programs. These routines were developed by TERADYNE, Inc. in conjunction with a VAX DBMS application which is now used by Teradyne's Customer Service Organization. .s Early on in the development cycle of the system we determined that there would be certain types of data that we would need to maintain that would not require any or would require very little in the way modifications. We quickly learned that a DBMS database was not the kind of place to be storing these small data sets. We experimented with the idea of having separate RMS files for each table and decided that this too was not going to suffice. In both cases the overhead involved in loading the tables was too costly. In certain programs up to ten different tables would need to be loaded and in the case of the RMS file idea the amount of time invloved in simply opening each of the separate table files was sufficient enough that we decided to look at other alternatives. The Remote Table concept was the result.