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 / asr002.doc < prev next >

Wrap

Text File | 1988-05-03 | 33.1 KB | 603 lines

.po 12 ..po 1 .he ASR Newsletter, Issue 2, May 1986 .fo Page # Ada (tm) Software Repository (ASR) Newsletter Issue 2, May 1986 Richard Conn, Newsletter Editor Published by Echelon, Inc. THIS ISSUE Page I. ADA TECHNOLOGY - SOME INSIGHTS 1 A. Experience in Ada Applications B. Bugs in Ada (and other) Compilers C. Judging Compilation/Linking Time for Ada Programs D. Is Ada a Hodgepodge Formed by Committee? E. More on the Complexity of Ada F. Weakness in Ada II. GENERAL INFORMATION 3 A. Access to the Ada Information Public Account B. Ada Information Clearinghouse Newsletter C. Validated Ada Computer for the IBM PC/AT III. NEWS ITEMS CONCERNING THE ADA SOFTWARE REPOSITORY 5 A. Data Dictionary Problem Resolved B. Rehosting Data Invited C. Hardcopy Documentation from Echelon D. Talks on the Ada Software Repository E. Access to the ASR from Europe F. Pending Termination of the ADA20 Accounts G. More on Alternate Access to the ASR IV. NEW SUBMISSIONS IN APRIL 7 V. HIGHLIGHTS OF SELECTED SUBMISSIONS 10 ============================================================================== I. ADA TECHNOLOGY - SOME INSIGHTS The following messages, reprinted with permission from electronic mail which appeared on the ADA-SW email list, provide some interesting insights into Ada technology and its applications. A. Experience in Ada Applications (by Edward Berard, EBERARD@USC-ISIF): "While there have been a good number of Ada success stories (contact Maj. Al Kopp at the Ada Joint Program Office), there have also been a number of failures. For example, Owen McOmber reported in February of 1985 that the SUBACS program was a failure (the Navy would be lucky, said McOmber, if they could salvage 50,000 lines of Ada code out of an estimated 2,000,000 lines written). McOmber went on to say that "continuing to push Ada for Ada's sake will kill the language." However, McOmber went on to acknowledge that, " the SUBACS failure was due to its ambitious schedule and that it would have failed regardless of the implementation language used." "We technologists often have a hard time differentiating between a bad idea and a bad implementation of a good idea. Any concept, including Ada technology, can be implemented so poorly that it appears that the original idea was ill-conceived. Further, since technologists and their managers often have a hard time accepting blame for any failures, it is often convenient to blame inanimate objects (e.g., the Ada programming language) for the failure of a project. (Remember the cliche about a poor workman blaming his tools.)" B. Bugs in Ada (and other) Compilers (by Edward Berard): "As recently as this year, I have had experiences with bug-ridden FORTRAN and C compilers. If you meant to imply that only Ada compilers have bugs, or that they are any more bug-ridden than compilers for other languages, you have an almost impossible task. A visit to any computer science department will turn up dozens of students who can break the compilers on the university's compilers (for all programming languages). "Quite a lot is demanded of Ada compilers. It has barely been three years since the ANSI/MIL-STD 1815A was established (February 17, 1983). It has been less than three years since the first Ada translator was validated (April 11, 1983). Considering that short time span, I am impressed with the state of Ada compiler technology. [As as exercise for your students, you might have them attempt to establish and compare the maturity of compilers for other languages, e.g., C, LISP, Pascal, and FORTRAN, when they were as old as Ada is today.] "If the fact that certain technology originates from the federal government, or from the Department of Defense, offends you, you may find that your offense diminishes with time. It is no secret that the technology associated with items such as airplanes, computers, and computer programming languages (remember COBOL?) was either originated or accelerated when it was deemed to be in the interest of national security. Fortunately, in time, most of the DoD's pet technologies lose their direct association with the DoD and are then evaluated by the masses on their own merits. [You might find it interesting to note that in Europe over 80% of the Ada applications are non- military, or that the Japanese are making extensive use of Ada technology (to my knowledge, none of it for military purposes).]" C. Judging Compilation/Linking Time for Ada Programs (by Edward Berard): "This is a classic case of being unable to distinguish between a language and its implementation. For example, the Rational Ada environment makes such changes surprisingly fast, especially for large programs. Further, even with other Ada systems, the compile and linking time can be significantly reduced via such things as subunits." D. Is Ada a Hodgepodge Formed by Committee? (by Edward Berard): "Any time I hear this kind of remark, I can be fairly certain that the originator is viewing Ada from a syntax-only perspective. Yes, if one has little or no formal software engineering education, Ada appears to be one of the most complex languages ever created. However, if one views the language as a vehicle for implementing modern software engineering, the language is very simple and straightforward. [For more of a software engineering perspective on Ada, you might wish to contact Dr. Charles McKay at the University of Houston, Clear Lake.] "Finally, while many people contributed to the design of the language, it is primarily the work of one man: Jean Ichbiah (now at Alsys, S.A.)." E. More on the Complexity of Ada (by Larry Carroll, LARRY@JPL-VLSI): "The only thing I would add to Ed Berard's comments is some comments of my own on the myth of Ada's complexity. I don't mean that Ada is NOT complex; rather I think we tend to underestimate the complexity of our favorite languages. We usually know them so well that we forget the trouble we had bending our minds around the new syntax and semantics of the language. Further, we usually have to get deeply involved with an operating system. In ForTran, for instance, to do real-time programming you have to have available and understand the interactions of a dozen or two subprograms, typically the ISA (Industrial Society of America, I believe) standard extensions. "Another universe of examples could be given in the C language. I'm peripherally involved in the process of porting a number of SW tools from Berkeley Unix to AT&T System V Unix and VAX-11 VMS. What a headache that is. There are at least three major types of concurrency involved and several variations on each. Dynamic memory and inter-process communication has the same problem. And different compilers treat pointers in subtly different ways that cause more problems than major differences would have. "It's for this reason that many C and Unix experts have been involved in efforts to create standards (ANSI X3J11 and IEEE P1003, respectively). And AT&T is gently pushing an upwardly compatible superset of C know as C++ which adds some of the features now available in Ada. (More specifically, C++ resembles Simula-67.) "So perhaps in a couple of years we'll be able to do in the C/Unix world what we can already do in Ada: insulate modules from each other and from the machine but still be able to tailor the entire system to specific hardware." F. Weakness in Ada (by Larry Carroll): "The one area in which Ada is weak is in its parallel processing capability. Every other aspect of Ada has been tested in actual production languages, though in (often only slightly) different form. Concurrency, however, is both inherently complex and an area of computer science that is still pretty much a frontier. Ada's minimal parallel-processing capability is probably a good thing. In 1988 when the Ada standard goes up for change I suspect this is where most of the changes will take place, building on the work of all of us who are trying to use Ada in real-time systems." ============================================================================== II. GENERAL INFORMATION A. ACCESS TO THE ADA INFORMATION PUBLIC ACCOUNT (quoted from email sent to INFO-ADA@ADA20 by Karl Nyberg, Nyberg@ADA20) A public computer account is available on USC-ISIF. The following details how to gain access to this account. Once logged in, the user can access the ASR (type the command "help ada-repository" for instructions). "The Ada-Information directory is a publicly available source of information on the Ada language and Ada activities. Sponsored by the Ada Joint Program Office and maintained by the Ada Information Clearinghouse, this computer directory is used to announce current events, general activities and indicate the status of various Ada compiler efforts. Access to the directory requires a computer terminal and modem or a personal computer and modem. The directory is resident on the University of Southern California Information Sciences Institute, System F (USC-ISIF), whose alias is Ada20, and is accessible via the Defense Data Network (DDN), GTE Telenet or a direct dialup connection through a modem. All of these methods will be explained in greater detail. I. Access via direct dialup "Direct dialup access is available by calling either (213)305-9172 or (213)305-8235 or (213)305-7971 "Once a connection is made, press return to receive the ISI-SYSTEM-F, TOPS-20 MONITOR 5 (7460) banner. Then procede to Section IV to log into Ada- Information. .pa II. Access via the DDN "The DDN is a collection of approximately eighty different computer networks representing DoD facilities, research centers and academia throughout the free world. All of the networks are packet-switching systems with interconnections at various locations. Access to the DDN is controlled by the Department of Defense and other responsible organizations. To obtain access to the DDN it is first necessary to have a computer directory or access to one on one of the several thousand host computers comprising the system. The AJPO maintains two hosts at the ISI facility in Southern California, the Ada20 and the Adavax. Access to these systems is controlled by the AJPO and is limited to those individuals providing a significant level of support to the Ada effort. Once access is obtained to one of these systems or to any other DDN host, the system administrator will provide directory and password information to the user. The following is the procedure for making a connection to the DDN and thence to the Ada20: "1. Dial the local telephone number provided by the system administrator to gain access to the DDN. "2. Press the Control and Q keys on the terminal keyboard simultaneously and the DDN banner should appear. If this does not occur, contact the system administrator for assistance. "3. Once the banner appears a connection may be established to the Ada20 @OPEN 26.2.0.103 TAC USERID: (your login code) ACCESS CODE: (your access code) Login OK TCP Trying...Open ISI-SYSTEM-F, TOPS-20 MONITOR 5 (7460) "4. See Section IV for information on how to log into Ada- Information III. Access through GTE Telenet "GTE Telenet is a private network run by GTE. Access to Telenet may obtained by contacting GTE for an account. To find the GTE office nearest you contact: GTE Telenet Communications Corporation 12490 Sunrise Valley Drive Reston, VA 22096 (800)336-0437 "Once you have a Telenet account, Ada-information may be accessed in the following manner: "1. Dial local Telenet number and establish a connection. "2. Press carriage return key 2-3 times, at which point Telenet responds with an @ prompt. "3. Once you receive the @ prompt a connection may be established with the Ada20. ID;213668/JOHNDOE (Carriage return) (213668 is the ID # of the Ada20, JOHNDOE should be replaced by your own Telenet account, for international users the ID # of the Ada20 is 311021300668) Password = 123456 (Carriage return) (Enter your 6 digit password number) "4. See Section IV for how to log into Ada-Information IV. Logging into Ada-Information "1. Wait for the @ prompt before logging in. @Ada-Information Ada (the second Ada will not appear as it the password and is not echoed.) "2. Help may be obtained by typing HELP after login. "Regular access to Ada-Information provides the latest update information on what's new in the Ada community. For additional information on anything in this pamphlet, please contact the Ada-Information Clearinghouse at (703) 685- 1477 or (301) 731-8894." B. ADA INFORMATION CLEARINGHOUSE NEWSLETTER The Ada Information Clearinghouse publishes a newsletter on the Ada effort. Contact 703/685-1477 to subscribe. C. VALIDATED ADA COMPILER FOR THE IBM PC/AT Company: Alsys, Inc. 1432 Main St. Waltham, MA 02154 617/890-0030 Cost: $3000 (in the US) Host Computer: IBM PC/AT Target Computers: IBM PC/XT or IBM PC/AT (8086 instructions) IBM PC/AT (80286 instructions) Note_1: 4M byte memory board included Note_2: Applications programs can access extended memory (up to 16M) Note_3: Data extracted from "Recent Microsystem Announcements" in IEEE Computer magazine, May, 1986 ============================================================================== III. NEWS ITEMS CONCERNING THE ADA SOFTWARE REPOSITORY A. DATA DICTIONARY PROBLEM RESOLVED. The problem reported in compiling the Data Dictionary tool (files DD*.* in PD:<ADA.PDL>) has been resolved. A new ABSTRACTIONS file from Intermetrics is required. This new file is contained in PD:<ADA.COMPONENTS> as NEWABS.*. The readme file for the Data Dictionary has been updated to point to this new abstractions file. There are now two ABSTRACTIONS files from Intermetrics. Both are in PD: <ADA.COMPONENTS>. ABSTRACT.SRC is to be used with NOSC/WIS tools 5.1.1, 5.1.2, 6.1.2, and 6.2. NEWABS.SRC is to be used with NOSC/WIS tools 4.1.1 and 4.1.2. B. REHOSTING DATA INVITED. Many users of the ASR are rehosting code from the ASR onto systems other than that on which the code was originally developed and targetted. These users are encouraged to submit their rehosted code and comments on their rehosting experiences to the ASR. C. HARDCOPY DOCUMENTATION FROM ECHELON. The User's Handbook project has been temporarily set aside in favor of a master index to all software in the ASR. This index contains details on every item of software in the repository, including information on the host and target computers and environments, listings of the associated files, and abstracts. The target date for availability of the first edition of this master index is 1 July. New editions will be issued as the ASR grows. D. TALKS ON THE ADA SOFTWARE REPOSITORY. Richard Conn, the maintainer of the Ada Software Repository, gave a presentation on the ASR and the DDN at the 11th Annual Trenton Computer Festival on Saturday, April 19. Attended by over 60 people, the talk was well-received and proved to be of value for the attendees. Consequently, such talks will continue to be scheduled. The next talk is set for Thursday, May 29, at the Air Force Institute of Technology, Wright-Patterson AFB, Ohio. This talk is given as a part of an Ada course which is presented to the faculty of the Electrical Engineering Department and funded by the Air Force Institute of Technology and the Air Force Office of Scientific Research. Attendance is restricted to military and civilian personnel at Wright-Patterson Air Force Base. There is no admission charge. For more information, contact: Lt Col Harold Carter, PhD Department of Electrical Engineering Air Force Institute of Technology AFIT/ENG Bldg 640 Wright-Patterson Air Force Base, OH 45433 513/255-6913 hcarter@AFIT-AB -- electronic mail is preferred The talk planned for NASA Johnson Spacecraft Center in Houston has been postponed indefinitely. Notice will be posted in this newsletter should it be rescheduled. E. ACCESS TO THE ASR FROM EUROPE. The ASR will soon be available online at the Stockholm Computing Center (QZ) in Sweden. Points of contact: Mats Ohlin (Mats_Ohlin_FOA2%QZCOM.MAILNET@MIT-MULTICS.ARPA) or Else-Karin Boestad-Nilsson Ada in Sweden Secreteriat c/o Swedish National Defense Research Institute Box 27 322 S-102 54 Stockholm, Sweden Else-Karin Boestad-Nilsson is secretary in AiS as well as editor for the Ada Europe Newsletter. F. PENDING TERMINATION OF ADA20 ACCOUNTS (quoted from an email message sent to ISIF-USERS by MARMSTRONG@ADA20). "The use of directories on the USC-ISIF host is sponsored jointly by the Ada Joint Program Office and the STARS Joint Program Office. Although the Ada Program has fulfilled its portion of the financial obligations for this support, no funding has yet been received from the STARS Program. As a result, use of USC-ISIF by all personnel for the Ada and STARS Programs may be terminated in the near future. You are hereby advised to retrieve all appropriate files in preparation for possible termination of support on USC- ISIF. "We regret the impact that the impending termination will have on the Ada and STARS Programs and will keep you advised if there are any changes to the current status of support." [Ed Note - this may affect the public account described in item A above] G. MORE ON ALTERNATE ACCESS TO THE ASR. Item E above shows one of the steps taken to give access to the ASR to members of the Ada community who do not have access to the DDN. Credit goes to Mats Ohlin and his associates. With the pending loss of the ADA20 accounts, it is important that subscribers to the ADA-SW email list who are now on ADA20 obtain a hardcopy subscription of the ASR newsletter from Echelon (call 415/948-3820, price is $16.00/year for 12 issues). As more sources to the software in the ASR become available, information will be published in the ASR newsletter. Four sources are being examined at this time. .pa ============================================================================== IV. NEW SUBMISSIONS IN APRIL ------------------------------------------------------------------------------ 1. NEW ABSTRACTIONS Components Library Files and Sizes (in Bytes): PD:<ADA.COMPONENTS> NEWABS.DIS 2768 .PRO 3319 .SRC 659811 Machine/System Compiled/Run on: DEC Ada / VMS Abstract: ABSTRACT.SRC in PD:<ADA.COMPONENTS> is the components library used by NOSC/WIS tools 5.1.1, 5.1.2, 6.1.2, and 6.2. NEWABS.SRC is used by tools 4.1.1 and 4.1.2. ------------------------------------------------------------------------------ 2. Design Requirements Traceability Package Files and Sizes (in Bytes): PD:<ADA.MANAGEMENT-TOOLS> RT.ABS 2503 RTGRM.LIS 37874 .CMM 627 RTREAD.ME 3348 .EXP 2640 RTSRC.DIS 1673 .LIS 37874 RTTEST.DAT 59084 .PRO 3915 .DIS 1576 .SRC 393200 RTUSER.MAN 16393 Note: NEWABS (see item 1 above) is required. Machine/System Compiled/Run on: Dec Ada / VMS Abstract: This tool is used to trace routines and declarations in the source code back to specific paragraphs in a requirements document. For each requirement referenced in a source file, the output listing shows what program units reference that requirement. An intermediate file containing the pairs (location in code, reference cited) can be saved for use in subsequent invocations. When used in this way, the output report can show requirements traced to more than one source file. ------------------------------------------------------------------------------ 3. Map Generator Tool Files and Sizes (in Bytes): PD:<ADA.TOOLS> WMGS.CMM 578 WMGSCMDFL.DIS 242 .MEN 11582 WMGSMATH.TST 5389 .PRO 3587 WMGSMENU.DIS 135 .SRC 304280 WMGSREAD.ME 118 WMGSBP.INP 191412 WMGSSRC.DIS 451 WMGSCMD.FLS 8608 Machine/System Compiled/Run on: TeleSoft 2.1 / VMS Abstract: Inputs from operator will define map details, define and label fixed points; optional inputs will define three-dimensional display. Generator allows views of the earth from different projections, incorporates zoom capability, displays specified areas of interest. ------------------------------------------------------------------------------ 4. Symbolic Debugger Files and Sizes (in Bytes): PD:<ADA.DEBUGGER> SD.ABS 1801 SDGRAMMAR.GRM 82491 .CMM 608 SDREAD.ME 5546 .HLP 12212 .ME2 238 .MAN 269466 SDTCF.DAT 2023 .PRO 4203 SDTEST.DAT 112103 .SRC 889057 .DIS 54 SD2.HLP 21414 Machine/System Compiled/Run on: DEC Ada / VMS Abstract: Interactive debugger will provide debugging and diagnostic aids at the Ada statement level through an "Ada-like" command language. Capabilities include: (1) Setting, resetting and displaying breakpoints; (2) Setting and displaying Ada program variables; (3) Tracing program execution at statement, block or unit level; (4) Snap dumps in printing format form or raw data form to occur periodically or on demand; (5) Execution frequency profiles for each Ada statement and entry/exit to each program block and unit, with optional report showing percentage of total execution time spent in each code block and in each statement within a block. Tool consists of source instrumentation module, debugger module and a report generator. ------------------------------------------------------------------------------ 5. File Compare Utilities Files and Sizes (in Bytes): PD:<ADA.COMPONENTS> FILECOMP.ADA 85866 .PRO 3808 Machine/System Compiled/Run on : DG MV10000, ROLM ADE VAX 11/780, DEC ACS RATIONAL R1000 Note: Requires package TOD_Utilities (see CDUPDATE). Abstract: This generic package contains routines to compare two ASCII files. It produces as output a side-by-side listing of both files, showing their differences in a very readable format, and also produces an update deck which can be used to provide a mapping between the two files. This update deck is meant to be input for a revision control package, called Context_Directed_ Update_Utilities. ------------------------------------------------------------------------------ 6. File Sorting Utilities Files and Sizes (in Bytes): PD:<ADA.COMPONENTS> SORTARRY.ADA 61880 .PRO 3252 Machine/System Compiled/Run on : DG MV10000, ROLM ADE VAX 11/780, DEC ACS RATIONAL R1000 Abstract: This generic package contains several array sorting routines. ------------------------------------------------------------------------------ 7. SQL DBMS Interface Files and Sizes (in Bytes): PD:<ADA.ADA-SQL> SQL.CMM 584 SQLDML.DAT 3845 .PRO 5050 .DIS 120 SQLDD2.DIS 75 .OUT 10333 .SRC 51795 .SRC 123991 SQLDDL.DIS 112 SQLDMLRD.ME 3072 .SRC 42642 SQLREADME.DOC 1299 SQLDDLRD.ME 2673 SQLSPC.INT 43318 SQLDDLTS.IN 2265 .TXT 140309 .OUT 4732 SQLSPCRD.ME 284 Machine/System Compiled/Run on: ROLM/DG / AOS Abstract: The HQ USAF Assistant Chief of Staff for Information Systems anticipates the adoption of SQL as the Air Force standard Relational data base query language. The Air Force will probably adopt the American National Standard (ANS) Database Language SQL as its Relational query language. A draft proposed American National Standard (dpANS)/International Standard Database Language SQL is in the public review process. Given the above Air Force position, the WIS JPMO began a project with the Institute for Defense Analysis and RACOM Computer Professionals to develop a standard Ada DBMS interface (Ada/SQL) based on the dpANS Database Language SQL. A "Proposed Binding Ada to Database Language SQL" has been presented to the responsible American National Standards Committee (X3H2). We anticipate its adoption as the DoD and ANS/ISO standard Ada relational DBMS interface and it will be the WIS Standard Ada DBMS interface. As such, we recommend the Ada/SQL interface be used for any development of an Ada DBMS interface. ------------------------------------------------------------------------------ 8. Other Updates and Additions A. Contract Data on the NOSC/WIS Tools. A new file has been added to PD:<ADA.WIS-ADA-TOOLS> which contains information on all contracts in the NOSC/WIS project. Files and Sizes (in Bytes): PD:<ADA.WIS-ADA-TOOLS> REFFILES.SRC 125533 B. Comment (Software Review) Files Updated. The following Comment (CMM) files have been updated. These contain brief reviews of the associated software packages. Files and Sizes (in Bytes): PD:<ADA.BENCHMARKS> PD:<ADA.MANAGEMENT-TOOLS> BENCHMARK.CMM 3266 MANAGE.CMM 1094 JPMOBENCH.CMM 3446 PPLANNER.CMM 774 PD:<ADA.COMPILATION-ORDER> TRACKER.CMM 1092 COMPORD.CMM 1456 PD:<ADA.MATH> PD:<ADA.COMPONENTS> MLIB2.CMM 615 CLI.CMM 2001 PD:<ADA.MENU> COUNTADA.CMM 1217 MMAN.CMM 1546 DSTR3.CMM 2068 MMGR.CMM 5079 Files and Sizes (in Bytes), Continued: PD:<ADA.DBMS> PD:<ADA.MESSAGE-HANDLING> MIMS.CMM 1061 GMHF.CMM 1359 PD:<ADA.DDN> UNITREP.CMM 886 FTPSMTP.CMM 1253 PD:<ADA.METRICS> TCPIP.CMM 1248 APATH.CMM 1355 TELNET.CMM 1264 PANAL.CMM 1333 PD:<ADA.EDITORS> PERFORM.CMM 1357 WP.CMM 1272 SINST.CMM 1345 PD:<ADA.FORMGEN> SMETRIC.CMM 1411 FORM2.CMM 1377 PD:<ADA.PRETTY-PRINTERS> PD:<ADA.GKS> FORMATTER.CMM 1327 GKS0A.CMM 2051 PRET.CMM 1340 GKSMA.CMM 2218 --------------------------------------------------- PD:<ADA.SIMULATION> PD:<ADA.STYLE> PD:<ADA.VIRTERM> QSAP.CMM 956 CHECK.CMM 1404 VT2.CMM 902 PD:<ADA.SPELLER> PROF.CMM 1368 SPELL2.CMM 1296 STND.CMM 1373 PD:<ADA.STUBBER> PD:<ADA.TOOLS> STUBBER.CMM 1797 CONSTRCT.CMM 572 ============================================================================== V. HIGHLIGHTS OF SELECTED SUBMISSIONS Three subdirectories of the ASR contain only general information. The following information is extracted from the talks I am currently giving. PD:<ADA.GENERAL> -- Contains information of general interest AAREAD.ME 1137 General Documentation ADAREPOS.DOC 1880 ARCHIVE.DOC 25914 CHECKOUT.DOC 1846 Checkout Procedure COPY1RT.DOC 4434 Information on Copyrights COPY2RT.DOC 5777 COPY3RT.DOC 11313 COPYRITE.DOC 22887 COPYRTGNU.DOC 6547 CRC.DOC 4998 Information on Cyclic Redundancy Checks DIRLIST.DOC 10177 Listing of all directories FINDME.DOC 1918 How to find things FTP.DOC 25914 How to use FTP FTP1.DOC 17334 FTP2.DOC 20267 FTPADAINF.DOC 2248 FTPECLB.DOC 5763 KERMIT.DOC 16560 Information about KERMIT KFLYER.DOC 6790 KMICRO.DOC 28992 LBR.DOC 952 Data on LBR Files MLIST.DOC 1456 Data on the ADA-SW email list OPERATE.DOC 1424 Statement of Operation PDLSURVEY.DOC 10491 PROLOGUE.ADA 1904 PROLOGUE Template .DOC 1581 PROLOGUE Documentation READTAPE.FOR 10000 FORTRAN Program to assist with tapes SAMPLE.PRO 2723 Sample PROLOGUE File SNAP01.DOC 3754 Snapshots SNAP02.DOC 10523 SUBMIT.DOC 4769 Submission Instructions TAPEDIST.DOC 966 Data on tape distribution USENET.DOC 2041 Data on USENET UUCPBIT.DOC 4808 Data on BITNET and UUCP WELCOME.DOC 46417 Welcome Message .PRO 1677 Prologue to Welcome Message PD:<ADA.EDUCATION> -- Educational Information ADA1FOR.DOC 5190 Ada/FORTRAN Interfacing ADA2FOR.DOC 1428 ADASOFTR.DOC 7802 Tech Reports BIBLIO.DOC 4369 Bibliography of Ada books BOOT.DOC 8646 Bootstrap Info FOR1ADA.DOC 2770 FORTRAN/Ada Interfacing GLOSSARY.DOC 25315 Glossary of Terms OBJECT.DOC 8793 Discussion: OOD PNOTE1.DOC 4834 Programming Notes PNOTE2.DOC 1948 PRODUCT.DOC 14059 PROGERRS.DOC 7494 Common Ada Programmer Errors TEXTS.DOC 26291 Ada Texts TITR.DOC 71075 Tech Reports TITRINTRO.DOC 1309 PD:<ADA.POINTERS> -- Pointers to Other Information Sources ADAINFO.DOC 5019 Ada Info on ADA20 ADAREFS.DOC 1683 References ARMYALS.DOC 327 ALS Data COMPILERS.DOC 13740 List of Validated Compilers DODD5000.DOC 11101 Directive 5000.31 ECLBENCH.DOC 3094 EVINFO.DOC 5967 E&V Data IBMPCADA.DOC 4660 IBM PC Ada Compilers NATOADA.DOC 1930 NATO Data SEI.DOC 398 SEI Data TEXTBOOKS.BIB 8918 Ada Text Books .DOC 86413 ============================================================================== Ada is a registered trademark, U.S. Government - Ada Joint Program Office. The following are trademarks of Digital Equipment Corporation: DEC, DECSYSTEM-20, ULTRIX, VAX, VMS. UNIX is a trademark of AT&T Bell Laboratories. The following are trademarks of Data General Corporation: AOS, ROLM. Verdix is a trademark of Verdix Corporation. The Ada Software Repository Newsletter is Copyright 1986 Echelon, Inc. All Rights Reserved. Permission to reprint, wholly or partially, is automatically granted if source credit is given to Echelon. Echelon, Inc. 885 N. San Antonio Road Los Altos, CA 94022 USA Telephone: 415/948-3820