From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: * X-Spam-Status: No, score=1.1 required=5.0 tests=BAYES_20,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!nosc!ucsd!ucbvax!VLSI.JPL.NASA.GOV!larry From: larry@VLSI.JPL.NASA.GOV Newsgroups: comp.lang.ada Subject: Ada Texts Message-ID: <880728110704.e5d@VLSI.JPL.NASA.GOV> Date: 28 Jul 88 18:07:04 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet List-Id: -- First, note that the correct spelling is Ada, not ADA. Ada is not an acronym. Second, if you can, copy from SIMTEL20.ARPA the four files from PD2: that can be specified as TEXT*.* and BIBLIO.DOC. They contain information and reviews on Ada books. Which book is best depends on the reader and their purposes. A good intro- ductory text that could be used by novice programmers is by Putnam Texel, (title forgotten, sorry), which starts with the package concept and gets students programming immediately. It is a top-down approach which avoids the more difficult Ada features. She has a second text (which hasn't been published yet, I believe) that tackles the rest of Ada. The book by Cohen mentioned a few days ago is the one I found most useful after I really got down to programming Ada. It gives a lot of examples and advice on how and when to use different features, and when not to. Some- times not even the clearest explanation of a language feature makes sense, and then a complete working example is invaluable. Larry @ jpl-vlsi