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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,ea4f04ec8d41f5b7 X-Google-Attributes: gid103376,public From: Ken Garlington Subject: Re: Ada83 equivalents for Ada95 Date: 1996/05/29 Message-ID: <31ABFED5.5793@lmtas.lmco.com>#1/1 X-Deja-AN: 157350180 references: <31A66DAA.7418@sud.ed.ray.com> content-type: text/plain; charset=us-ascii organization: Lockheed Martin Tactical Aircraft Systems mime-version: 1.0 newsgroups: comp.lang.ada x-mailer: Mozilla 2.01 (Macintosh; I; 68K) Date: 1996-05-29T00:00:00+00:00 List-Id: Robert A Duff wrote: > > In article , > Brad Balfour wrote: > >There are even tools available that you can purchase which will > >automatically detect these problems in your Ada 83 code. > > Which tools are those? Two non-compiler tools promoted at TRI-Ada '95 that look for Ada 95 incompatibilities in Ada 83 code: * Ada-ASSURED 3.0 from GrammaTech (info@grammatech.com) * Ada9X Transition Aid from Software Compositions (swcinfo@aol.com) -- LMTAS - "Our Brand Means Quality"