Programmer's ROM - The Computer Language Library

home *** CD-ROM | disk | FTP | other *** search

/ Programmer's ROM - The Computer Language Library / programmersrom.iso / ada / news / asr102.doc < prev next >

Wrap

Text File | 1988-05-03 | 49.4 KB | 855 lines

Ada Software Repository Newsletter Issue 102, December 1987 Ada Software Repository (ASR) Newsletter Edited By Richard Conn Manager, Ada Software Repository Published By Management Assistance Corporation of America (MACA) PO Drawer 100 - Building T148 White Sands Missile Range, New Mexico 88002 505/678-3288 THIS ISSUE ---------- Page I. Articles Section 2 "Some Thoughts on Software Reusability and Ada" 2 by Richard Conn II. Release Notices 8 1. Welcome Message and Disk References Changed 8 2. Rationale for Ada 8 3. Info on Network Protocols in Ada 8 4. Source of Booch's "Software Components" Available 9 5. AdaIC Newsletter V.1 Released 9 6. ASR Taxonomy Released 9 7. ASR Usage Statistic 12 8. Questions about Abstractions 12 9. Utility to Write VAX/ANSI Tapes on Data General Released 13 10. String Comparison Package Released 14 The Ada Software Repository and this Newsletter are sponsored by The STARS Joint Program Office, The Pentagon and The US Army Information Systems Command, White Sands Missile Range ------------------------------- DISCLAIMER: Statements made in this newsletter are the opinions of the individuals making them and are not necessarily the opinions or policy statements of the US Government or any other organization. Ada Software Repository Newsletter Issue 102, December 1987 I. "Some Thoughts on Software software, and (5) how to ensure the Reusability and Ada" reliability of the reusable by Richard Conn software. There are also many political issues associated with This article is composed of making reuse possible: (1) how to the essence of a paper presented at instill a sense of confidence in the Army Micro/Info '87 Conference the software, (2) how to pay for in Kansas City during August, 1987. the establishment and maintenance of a reusable software library, (3) how to charge our customer when we 1. SOFTWARE: TO REUSE OR NOT TO reuse software, (4) how to provide REUSE an incentive to our contractors to ----------------------------------- reduce our costs by reusing Software reusability is a software, and (5) how to reduce the double-edged sword. On one side, cost and schedule risks associated it intuitively sounds like a good with reusing software. From the idea. We would not reinvent the point of view of the Company, how wheel; we would save time and money does software reuse affect the by producing a product out of a bottom line, the profit margin? collection of components that were Can we save money by establishing a already tried and proven; we will reusable software library? have to spend less time in testing because many parts of our system 2. SOFTWARE REUSABILITY AND THE DOD would have already been extensively ----------------------------------- tested. The US Department of Defense On the other side, there (DoD) has studied the pros and cons are reasons for not reusing of software reusability for quite software. If I am paid by how many some time, and it has decided that lines of code I write, why should I software reusability and a common do something to reduce my income? computer language, Ada, are keys to How do I charge my customer for my the solution of its software system when parts of it were not problems. The DoD has an intense written by me? Why should I pay interest in reducing its software (in terms of dollars, code size, costs and simultaneously increasing and code execution speed) for the the reliability of its software and additional code someone puts into a the productivity of its software module that my application contractors. The cost of software does not need? How do I know that maintenance in mission-critical a piece of software in some library systems within the Air Force alone really works as advertised without was $2.5B/year in 1985, is bugs? If I'm handed a piece of $3.6B/year today (1987), and is software out of a library, how do I expected to reach $7.3B/year by know that I won't spend more time 1996 if the current trend trying to figure out what it does, continues[1]. Clearly, the whether or not it works, and how to importance of software in our major modify it for my application than I weapons systems is increasing: the would if I wrote it myself? F-4's flown in Vietnam in 1974 There are many technical contained just a few processors, issues associated with making the the F-16A in 1981 contained seven reuse of software possible: (1) how computer systems (50 processors) to determine what should be reused, and 135K lines of code, the F-16D (2) how to design for reuse, (3) in 1986 contained fifteen computer how to design with reusable systems (300 processors) and 236K software, (4) how to classify, lines of code, and the Advanced store, and retrieve reusable Tactical Fighter now under Articles, Page 2 Ada Software Repository Newsletter Issue 102, December 1987 development is expected to contain 3. SOFTWARE REUSE AND COMPUTER over 12M lines of code (all of LANGUAGES which is to be written in Ada). ----------------------------------- The DoD Software Initiative is Reuse of software is not a new based around three main programs: concept, but, before the advent of (1) the Ada programming language, Ada, several impediments have which is managed by the Ada Joint prevented software reusability from Program Office and provides a becoming really effective. In most common technical base, (2) the projects there was a distinct lack Software Engineering Institute of incentives to aggressively (SEI), which is managed by the SEI encourage reusability (see my Joint Program Office and is tasked opening remarks in this paper). to accelerate the transition of new Most languages did not have the software technology into practice, proper facilities to support the and (3) the Software Technology for development of reusable software Adaptable, Reliable Systems (STARS) components, and reuse with these program, which is managed by the languages meant writing modules STARS Joint Program Office and is which performed distinct functions tasked with inventing a new way of on particular types of objects doing software engineering, thereby (such as the software found in the increasing software productivity UNIX/C libraries and many libraries and reliability. Ada is the of commonly-used assembly language cornerstone for all three programs, routines). There was a lack of and software reusability based on language standardization (as Ada is a key to their success. evidenced by the many dialects of In discussing software FORTRAN and the different sets of reusability and the DoD, the STARS library routines found with program is of particular interest. different C compilers). There were STARS is divided into four many cultural and social roadblocks subprograms: (1) Foundations, to software reuse, including an whose mission is to create a educational system which encouraged "critical mass" of reusable reinventing software rather than software components and tools, (2) reusing software[3]. Efficiency the Competing Prime Lead Contracts, was an overriding concern in our whose mission is to develop and older, resource-limited computers, demonstrate a tailorable software and custom, hand-optimized code was engineering environment in which the prevailing approach; today, software reusability is extensively with processors having advanced employed, (3) Shadows, which significantly in terms of memory introduces the new software capacity and processing power, it engineering environment and has become permissible to sacrifice techniques (including reusability) some efficiency in order to improve to several candidate DoD projects, productivity and software and (4) Research by the service reliability. laboratories, which provides a Ada's standardization (through pragmatic assessment of the ANSI/MIL-STD-1815A and the Ada progress of the STARS program. The compiler validation procedures five-year STARS program roadmap mandated and enforced by the Ada (which has already begun with the Joint Program Office), some of its launch of 33 development efforts special features (such as generics, under the Foundations subprogram) packages, and separate is shown in Figure A[2]. compilation), and the cultural backing of Ada (through the DoD and its Software Initiative) make Ada especially suitable for promoting Articles, Page 3 Ada Software Repository Newsletter Issue 102, December 1987 software reuse. However, by simply protocol TCP/IP (Transmission using Ada, software does not Control Protocol/Internet automatically become reusable. Protocol). The DDN provides a Rather, Ada provides facilities common communications path for a which, in turn, make software reuse wide variety of computers, allowing more feasible. Ada allows the users of these computers to interfaces to be defined so transmit electronic mail and files functions performed by a software between each other. module are clear and precisely The value of a computer regulated. Ada's generics facility network to support software allows algorithms to be expressed reusability and exchange was in a common form which can be later realized for some time, and in 1979 instantiated for a particular need one of the first software (such as in writing a sort routine repositories on a major computer as a generic and later network, the CP/M software instantiating it to sort integers, repository on the ARPANET (the floating point numbers, strings, or Advanced Research Projects Agency certain types of records). There computer network) was set up on the is only one Ada, MIL-STD-1815A, MACSYMA Corsortium ARPANET host with no supersets or subsets, and computer at MIT. Supported by the the definition of Ada includes a INFO-CPM electronic mailing list, collection of standard library public domain software would be routines (such as TEXT_IO). There placed into a collection of are many Ada compilers for a wide directories on this computer, an variety of computers (the August electronic mail message would be 1987 list of validated Ada sent to the INFO-CPM electronic compilers[4] lists 101 Ada mailing list (where the message compilers), and transportable Ada would be duplicated hundreds of software can be written using any times and retransmitted one of these compilers, moved to a individually to members of this different computer, and recompiled list) announcing the new software, without any modification by another and the users would electronically of these compilers. transfer the software from MIT to their local ARPANET host computers, 4. THE ADA SOFTWARE REPOSITORY download it to their ------------------------------ microcomputers, and use it. Attempts at software The popularity and success of reusability of component libraries the CP/M software repository at MIT and tools have been with us for a attracted the interest and long time, and both the DoD and attention of the DoD, particularly industry have invested a lot of DARCOM, and, in 1983 when the effort in attempting to reuse MACSYMA Consortium was dissolved, software effectively. Of the CP/M software repository became particular interest is the effort sponsored by DARCOM and was moved sponsored by the Army's Materiel to SIMTEL20, a DDN-based host Command (AMC, formerly known as the computer at White Sands Missile Department of the Army Readiness Range in New Mexico. The DARCOM Command, or DARCOM) on the Defense Microcomputer Software Sharing Data Network (DDN)[5]. Today's DDN System (DMSSS) was established, and is quite probably the largest the CP/M software repository computer-based communications media flourished. The DMSSS organization in the world, being composed of was composed of only a few people over 400 computer networks which who were strong advocates of the are interoperating by means of the concept of sharing software in this DoD computer communications manner and willing to volunteer Articles, Page 4 Ada Software Repository Newsletter Issue 102, December 1987 their time and effort to make this Sands to purchase computer venture a reality. The people in equipment in support of the ASR DMSSS were motivated far more by activity and made plans to provide interest and enthusiasm rather than the software acquired through its money, and sponsors at DARCOM felt Foundations subprogram to the ASR. it was worthwhile to give these The ASR today contains over 43M individuals access to SIMTEL20 and bytes of Ada software and other support as required (such as information, including most of the legal and security counsel) to software in the WIS/NOSC toolset encourage the DMSSS group to (representing an investment of continue its efforts. Many other $5.5M), and supports a user software repositories maintained community estimated to be as large and operated by the DMSSS group as 10,000 people that have made have since sprung up on SIMTEL20 over 170,000 individual accesses to (see Figure B). the files in the ASR. Figure C The Ada Software Repository lists the major categories of (ASR) is one of the repositories software and information in the maintained by a member of the DMSSS ASR. group. Started in late 1984, the The picture painted above is ASR was approved, set up, and quite positive about software placed into operation literally reusability with Ada and the overnight, and interest in the ASR implementation of the Ada Software was immediately apparent. An Repository, but the arguments announcement of the ASR was made to presented at the beginning of this the INFO-ADA mailing list (which is paper on whether or not to reuse sponsored by the Ada Joint Program software should not be forgotten. Office), and users of the DDN and Perhaps the single most important other networks communicating with thing accomplished by the the DDN via electronic mail were implementation of the ASR is simply invited to subscribe to the ADA-SW that the ASR has shown that the electronic mailing list which effective reuse of Ada software on serviced the ASR. Software a massive scale is quite possible, immediately began to trickle in, but we don't yet have all the and the user community of the ASR answers. A large number of lessons rapidly grew. Colonel Bill have been learned by the DMSSS Whitaker of the World-Wide Military group (details of which are beyond Command and Control (WWMCCS) the scope of this paper), and there Information Systems (WIS, which is a lot of questions yet to be stands for WWMCCS Information resolved. Much research by Systems) organization observed the industry, academia, and the DoD ASR activity, and, having funded (the STARS program in particular) for the development of several is still underway in the area of million dollars worth of Ada software reusability. While the software components and tools in a ASR is quite popular, the software joint WIS/NOSC (Naval Oceans it contains is not perfect and Systems Center) Ada toolset trusted; each item of software in project, decided to provide this the ASR comes with a disclaimer software to the ASR in further that the software is provided "as- support of the ASR activity and the is" and should be thoroughly tested DoD Software Initiative as a whole. before being relied upon, and, Colonel Joe Greene, Director of the while some items in the ASR have STARS Joint Program Office, also been shown to be quite worthwhile, perceived the ASR activity to be of others have been shown to contain value to the STARS program, and, in both major and minor bugs. To 1987, STARS sent funds to White create a generation of software Articles, Page 5 Ada Software Repository Newsletter Issue 102, December 1987 which is made available through a [3] "Software Reuse: Motivators and mechanism like the ASR and is Inhibitors" by Will Tracz in the completely trusted will require an Proceedings of IEEE COMPCON, enormous investment of time, money, February, 1987. and effort, and the STARS program and other programs with similar [4] Ada Information Clearinghouse, goals in industry and academia are 3 August 1987 list of Validated Ada taking the first steps to make this Compilers, obtained from the Ada investment. As mentioned above, Software Repository on the Defense there are both technical and Data Network political problems to be overcome, and I am not yet convinced that we [5] See "The Ada Software will be successful in overcoming Repository and the Defense Data them. Network: A Resource Handbook" by Richard Conn (the author of this 5. FINDING OUT MORE paper) for more details of the DDN, ------------------- the ASR, and the DMSSS group. This If you are inspired to find book is published by New York out more about what is going on Zoetrope, 838 Broadway, New York, with software reusability, Ada, NY, 800/242-7546. STARS, and other related efforts, the list of references at the end [6] The first twelve issues of the of this paper is a good place to ASR Newsletter are available in start. If you have access to the hardcopy from Echelon, Inc., 885 N. DDN, you can subscribe to ADA-SW by San Antonio Road, Los Altos, CA sending electronic mail to ADA-SW- 94022, 415/948-3820 for a minor REQUEST@SIMTEL20.ARPA. If you do cost. All issues of the ASR or do not have access to the DDN, Newsletter are stored in electronic you can acquire the Resource form within the ASR itself in the Handbook[5], the ASR Newsletters subdirectory PD:<ADA.NEWS>, so if [6], and a copy of the ASR itself you have access to the DDN or are (see the Resource Handbook and the planning to acquire a tape of the ASR Newsletters for details). If ASR, you may wish to get the you are just now being introduced newsletters through the ASR itself. to Ada or have been working with Ada and want to find out more, the [7] The "Ada Adoption Handbook: A Program Manager's Guide published Program Manager's Guide, Version by the Software Engineering 1.0" by John Foreman and John Institute[7] should be of interest. Goodenough of the Software Engineering Institute is available 6. REFERENCES as Technical Report CMU/SEI-87-TR- ------------- 9, ESD-TR-87-110, May 1987 from the [1] Air Force cost and computer SEI, phone 412/268-7630. This resource figures extracted from the covers some concepts and presents "Air Force Software Management the several individuals' opinions Initiatives" briefing by Major on issues such as program manager General Merlin T. Smith, HQ Air considerations in moving to Ada Force Systems Command, during Ada (such as costs, technical issues, Expo '86. program control, and getting help), software production technology [2] "STARS Development Roadmap" was (including Ada compiler validation extracted from a briefing given by and programming support Col. Joe Greene, Director of the environments), the maturity and STARS Joint Program Office, at the applicability of Ada (especially to STARS Ada Foundations Workshop. embedded, real-time, and Articles, Page 6 Ada Software Repository Newsletter Issue 102, December 1987 distributed systems), other languages and mixing Ada with other languages, software reuse with Ada, and Ada training. Disclaimer: "The ideas and findings in this report should not be construed as an official DoD position. It is published in the interest of scientific and technical information exchange." Articles, Page 7 Ada Software Repository Newsletter Issue 102, December 1987 II. Release Notices under contract), as well as a great deal of other Ada-related ----------------------------------- information. You can get on their 1. Welcome Message and Disk mailing list by writing or calling: References Changed AdaIC The Welcome Message and 3D139 (1211 S. Fern, C-107) associated files have been updated The Pentagon to reflect the PD2: disk references Washington DC 20301-3081 as opposed to the old PD:. You can (703) 685-1477 get WELCOME.DOC from ----------------------------------- PD2:<ADA.GENERAL> 3. Info on Network Protocols in Ada Date: Fri, 11 Dec 87 09:40:14 EST or send an email request to From: csed-1!csed-20!baldo@hc.dspo.gov ADA-SW-REQUEST@SIMTEL20.ARPA. (James Baldo) ----------------------------------- Anyone interested in discussing the 2. Rationale for Ada design or implementation of Ada Date: Tue 8 Dec 87 06:30:08-PDT TCP/IP protocols can contact the From: author at the following address: ALLEN_S%ASD.SPAN@STAR.STANFORD.EDU (Stanley Roger Allen, AdaDude) James Baldo Jr. Institute for Defense Analyses The book "Rationale for the 1801 N. Beauregard St. Design of the Green Language" is Alexandria, VA 22311 now called (you guessed it) "Rationale for the Design of the 703-824-5516 Ada Language". The AJPO does not e-mail address: distribute this book directly, but baldo!csed-1.uucp@hc.dspo.gov it is the "source" of the document. Distribution is handled by the I am currently attempting to assist National Technical Information BDM in testing the code for Service (NTIS) and a couple of potential use in some STARS work other agencies. They are availible they are doing. IDA is currently at the following address/phone#: working on an X.400 MHS (1988) Remote User implementation in Ada National Technical Information funded under STARS. The emphasis in Service this work is to explore the design US Dept of Commerce and use of reusable software 5285 Port Royal Road components. IDA is also examining Springfield, Virginia 22161 the relationship between (703) 487-4650 communication software and Ada. The Rationale will cost a certain For those interested in the NOSC amount (I don't know just how much) TCP/IP protocols, Van Baker and I and you have to order it by its publish a lessons learned paper on order number -- AD A073 854. the project in Defense Electronics which appreared in their December The AJPO's Ada Information 1986 issue. Clearinghouse has a lengthy list of Ada documents produced by different parts of the govt (though a lot of them were developed by companies Release Notices, Page 8 Ada Software Repository Newsletter Issue 102, December 1987 ----------------------------------- ----------------------------------- 4. Source of Booch's "Software 6. ASR Taxonomy Released Components" Available Release of: ASR Taxonomy, 1/5/88 Date: Mon, 14 Dec 87 11:24:02 EST From: gbooch@ajpo.sei.cmu.edu 6.1. Taxonomy: Ada Software Repository Have you seen my book, "Software Introductory Information Components with Ada"? All of the Contents and Use of ASR software listed in appendix b of this book (some 501 packages) are 6.2. Abstract: available from me on tape. If you Several files in the top-level send me your address, I'll mail you PD2:<ADA> directory contain some information. information on the contents of the Ada Software Repository. These ----------------------------------- files are: 5. AdaIC Newsletter V.1 Released ADA.CRCLST ADA.RPT Release of: AdaIC Newsletter, Vol ADA.SNP 5, Issue 1 (AIC51.DOC) ADA.TAX ADA.UUE 5.1. Taxonomy: and Ada Books and Documents FILEUSE.DOC AdaIC Newsletters Unlike the majority of files 5.2. Abstract: in the ASR, these files are updated These files are Newsletters frequently by the maintainer of the put out by the Ada Information ASR in order to reflect changes Clearinghouse. They are made to the Ada Software recommended reading. Repository. AIC51.DOC (April 1987) is not -- ADA.CRCLST and ADA.UUE -- the latest AdaIC newsletter. AIC53 ADA.CRCLST contains a listing (Dec 87) is. I hope to post AIC52 of all the files in the ASR by and AIC53 in the near future (when directory. This listing includes I get a copy). the type of the file (always ASCII for the ASR), the size of each file 5.3. Directory Listing: in bytes, and a CRC (Cyclic Directory PD2:<ADA.NEWS> Redundancy Check) value for the File Name Byte Count Line Count file. The CRC value is useful in ------------- ---------- ---------- verifying that a given file was AIC42.DOC 31301 715 correctly transferred from the ASR AIC43.DOC 41422 1097 into the user's environment; if the AIC44.DOC 32581 629 CRC of a file computed by a CRC AIC51.DOC 17920 372 Check program on the user's ============= ========== ========== computer matches the CRC in this 4 Files 123224 2813 list, the user is assured that no errors occurred in file transfer. There are many CRC Check programs for various environments (UNIX, IBM PC, etc) scattered throughout the various repositories on SIMTEL20. ADA.UUE is a copy of ADA.CRCLST that has been ARCed and then UUENCODED. This process Release Notices, Page 9 Ada Software Repository Newsletter Issue 102, December 1987 significantly reduces the size of -- ADA.RPT -- the ADA.CRCLST file for transfer, ADA.RPT is a report similiar thereby expediting the file to ADA.CRCLST except that a PAGER transfer process IF the user has Hash code is provided instead of a the ability on his host computer to CRC value, and a line count is decode the file (via UUENCODE) and given for each file (a line is the un-ARC it. terminated by an end-of-line A sample listing of the first character, as opposed to an Ada few lines of the ADA.CRCLST file statement which is terminated by a looks like Figure 1. semicolon). The PAGER Hash code is =========================================================================== Figure 1: Partial ADA.CRCLST File Listing created Wednesday, December 30, 1987 15:22:01 Filename Type Bytes CRC PD2:<ADA.ADA-SQL> DAMES.CMM.1 ASCII 833 F5C0H DAMES.DOC.1 ASCII 5283 9A53H DAMES.PRO.2 ASCII 4913 4A99H DAMES.SRC.1 ASCII 616438 EE39H DAMESABS.DOC.1 ASCII 2139 68A7H ============================================================================ generated by the PAGER tool (not -- ADA.SNP -- PAGER2, however) and by the FCHECK The ADA.SNP file documents the tool in the ASR, so the validity of sizes of each of the directories of a transferred file can be checked the ASR. The number of bytes and by using programs written in Ada lines of source code and rather than a CRC Check program (no documentation in each directory is Ada implementation is known to presented, and a summary of the exist yet). entire Ada Software Repository is A sample listing of the first presented at the end of the report. few lines of the ADA.RPT file looks A sample listing of the first like Figure 2. few lines of ADA.SNP is in Fig 3. =========================================================================== Figure 2: Partial ADA.RPT File Directory and File Name Char Count Line Count Hash ----------------------- ---------- ---------- ---- PD2:<ADA.ADA-SQL> DAMES.CMM.1 833 36 84 DAMES.DOC.1 5283 125 32 DAMES.PRO.2 4913 99 115 DAMES.SRC.1 616438 13534 73 DAMESABS.DOC.1 2139 46 42 =========================================================================== Release Notices, Page 10 Ada Software Repository Newsletter Issue 102, December 1987 =========================================================================== Figure 3: Partial ADA.SNP File ---- Source Code ---- | --- Documentation --- Directory Byte Count Line Count | Byte Count Line Count ----------------------- ---------- ---------- | ---------- ---------- PD:<ADA.ADA-SQL> 1117750 30503 | 249705 6067 PD:<ADA.AI> 250984 7326 | 326909 10503 PD:<ADA.ANSI-LRM> 0 0 | 1201050 46091 PD:<ADA.BENCHMARKS> 1844998 65965 | 546636 19174 PD:<ADA.CAIS> 1719047 50360 | 10742 216 PD:<ADA.CAIS-TOOLS> 152675 4442 | 7140 132 PD:<ADA.COMPILATION-ORDER> 359990 8147 | 86428 2790 =========================================================================== -- ADA.TAX -- COMMUNICATIONS The file ADA.TAX contains a MESSAGE HANDLING listing of the current taxonomy of RAINFORM the Ada Software Repository. UNITREP SOFTWARE MODEL Internal to the ASR support PROTOCOL programs, the taxonomy is FTP/SMTP maintained as an acyclic graph, but SMTP ADA.TAX presents it as a tree. TCP/IP This taxonomy dynamically changes TELNET (typically as an upward-compatible extension to previous versions of COMPONENTS the taxonomy) as the ASR grows. CHARACTER SET The following is a listing of COMMAND LANGUAGE INTERPRETER a part of ADA.TAX: COMPOOLS IN ADA CONTEXT-DIRECTED UPDATE BENCHMARKS COUNT ADA STATEMENTS GENERAL COUNT OF ADA STATEMENTS 1 CAPACITY COUNT OF ADA STATEMENTS 2 COMPUTATION-INTENSIVE, COUNT OF ADA STATEMENTS 3 RECURSIVE PERFORMANCE ISSUES -- FILEUSE.DOC -- LANGUAGE COMPARISON FILEUSE.DOC lists all files in ADA, C, FORTRAN, PASCAL the subdirectories under PD2:<ADA> TASKING in order of the number of accesses. TASKING 1 Presented are the directory and TASKING 2 file name, the total number of accesses, the average monthly rate CAIS of access, and the size of the file SPECIFIC IMPLEMENTATION in terms of 2048-byte disk pages. MITRE CAIS Figure 4 is a sample of the EDITOR first few lines of a typical SOURCE CODE FILEUSE.DOC file: TEST ROUTINES Release Notices, Page 11 Ada Software Repository Newsletter Issue 102, December 1987 =========================================================================== Figure 4: Partial FILEUSE.DOC File [PHOTO: Recording initiated Wed 30-Dec-87 3:32PM] @ name # refs, rate/month, size. <ADA.COMPONENTS>LIST.ADA.2 502 13 7 pgs <ADA.COMPONENTS>ABSTRACT.SRC.1 467 15 224 pgs <ADA.PAGER>PAGER.SRC.5 456 17 34 pgs <ADA.BENCHMARKS>BENCH.DOC.1 451 15 3 pgs <ADA.AI>EXPERT.ADA.1 445 17 15 pgs =========================================================================== 6.3. Directory Listing: 8.1. Taxonomy: Directory PD2:<ADA> COMPONENTS File Name Byte Count Line Count LIBRARY ------------- ---------- ---------- ABSTRACTIONS ADA.CRCLST 38048 1103 and ADA.RPT 68488 1101 COMPONENTS ADA.SNP 3638 48 BINARY TREES ADA.TAX 5641 253 ABSTRACTIONS ADA.UUE 35 4 and FILEUSE.DOC 79042 1032 COMPONENTS ============= ========== ========== COMMAND LINE INTERFACE 6 Files 194892 3541 ABSTRACTIONS and ----------------------------------- COMPONENTS 7. ASR Usage Statistic DYNAMIC ARRAY ABSTRACTIONS Date: Tue, 5 Jan 88 04:40:23 MST and From: COMPONENTS Rick Conn <RCONN@SIMTEL20.ARPA> FILE MANAGER ABSTRACTIONS As of 1/5/88, the 1024 files and in the Ada Software Repository have COMPONENTS been accessed a total of 207,035 LEXICAL ANALYZER times. ABSTRACTIONS and ----------------------------------- COMPONENTS 8. Questions about Abstractions LINKED_LISTS SINGLY-LINKED LIST The recent notice about the ABSTRACTIONS popular files in the ASR has raised and some questions about what COMPONENTS ABSTRACTIONS is. As a general OUTPUT PAGINATION answer, the following release ABSTRACTIONS notice is attached. Note that and ABSTRACTIONS is the second most COMPONENTS popular item in the ASR. PARSER ABSTRACTIONS Release of: Abstractions and Release Notices, Page 12 Ada Software Repository Newsletter Issue 102, December 1987 COMPONENTS Linked Lists STACK Parser, Table-Driven ABSTRACTIONS Set Manipulation and (Normal and Ordered Sets) COMPONENTS Sorting STRING MANIPULATION Stack Manipulation ABSTRACTIONS String Manipulation and String Scanning COMPONENTS STRING SCANNER ABSTRACTIONS is used by ABSTRACTIONS NOSC/WIS tools 5.1.1, 5.1.2, 6.1.2, and and 6.2. See also MATH NEW_ABSTRACTIONS. DIRECTED ACYCLIC GRAPH ABSTRACTIONS 8.4. Directory Listing: and Directory PD:<ADA.COMPONENTS> MATH File Name Byte Count Line Count HASHING FUNCTIONS ------------- ---------- ---------- ABSTRACTIONS ABSTRACT.CMM 2263 57 and ABSTRACT.CO 2657 51 MATH ABSTRACT.PRO 3334 74 ORDERED SET MANIPULATION ABSTRACT.SRC 572620 17976 ABSTRACTIONS ============= ========== ========== and 4 Files 580874 18158 MATH SET MANIPULATION ----------------------------------- ABSTRACTIONS 9. Utility to Write VAX/ANSI Tapes on Data General Released 8.2. Author: Bill Toscano, Michael Gordon Release of: Write VAX/ANSI Tape Intermetrics, Inc, from Data General 733 Concord Ave Cambridge, MA 02138 9.1. Taxonomy: Contact: Lt. Colonel Falgiano TOOLS ESD/SCW WRITE VAX/ANSI TAPE FROM DG Hanscom AFB, MA 01731 9.2. Author: 8.3. Abstract: H. J. Clarke, A. F. Niessner, Jr. ABSTRACTIONS contains a number ARL/Penn State University of low-level support routines P.O. Box 30 which are used by NOSC tools State College, Pa. 16804 created by Intermetrics. Several routines are of general utility. 9.3. Abstract: The program, Vax_Tape, it's Included in ABSTRACTIONS are supporting packages, and the packages and routines for: acompaning CLI's, provide a Binary Tree Manipulation capability to write text files on a Command Line Interfacing Vax compatable, ANSI standard, tape (host-dependent) on a Data General MV10000. The Dynamic Acyclic Graph dynamic strings package, DYN, found Dynamic Arrays in the Ada Repository in the File Management subdirectory, PD2:<ADA.COMPONENTS>, (host-dependent) and named DSTR3.SRC, is used by Hashing this program. Lexical Analysis Release Notices, Page 13 Ada Software Repository Newsletter Issue 102, December 1987 9.4. Directory Listing: 10.4. Directory Listing: Directory PD2:<ADA.TOOLS> Directory PD2:<ADA.COMPONENTS> File Name Byte Count Line Count File Name Byte Count Line Count ------------- ---------- ---------- ------------- ---------- ---------- VAXTAPE.DOC 7446 166 STRCOMP.DOC 7270 165 VAXTAPE.PRO 2816 68 STRCOMP.PRO 2656 67 VAXTAPE.SRC 25344 844 STRCOMP.SRC 45586 1072 ============= ========== ========== ============= ========== ========== 3 Files 35606 1078 3 Files 55512 1304 ----------------------------------- 10. String Comparison Package Released Release of: String Comparison package 10.1. Taxonomy: COMPONENTS STRING COMPARISON 10.2. Author: Erland Sommarskog ENEA Data, Stockholm 10.3. Abstract: Article 219 of comp.sources.misc: This posting contains a package for string-comparisons in a fairly sophisticated way where regard to accents, non-letters and case is only taken if necessary. The user defines how each character should be sorted, whether if it is a letter, and whether it is a variant of another letter. See READ.ME [STRCOMP.DOC] for complete description. The purpose is not to provide a facility, though, rather to demonstrate the idea. The code is in Ada. Comments and questions are welcome to: Erland Sommarskog ENEA Data, Stockholm sommar@enea Release Notices, Page 14