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,4c9aaf040659caf8 X-Google-Attributes: gid103376,public From: eachus@spectre.mitre.org (Robert I. Eachus) Subject: Re: (unverified) Ada mandate cancelled (Greg A would be proud) Date: 1997/03/10 Message-ID: #1/1 X-Deja-AN: 224481173 References: <3.0.32.19970307192557.009979a0@iu.net> Organization: The Mitre Corp., Bedford, MA. Newsgroups: comp.lang.ada Date: 1997-03-10T00:00:00+00:00 List-Id: In article dewar@merv.cs.nyu.edu (Robert Dewar) writes: > The idea of making Ada a preferred technology rather than > mandating it might very well be advantageous even from an Ada > advocate's point of view. Far too often now, Ada is mandated, but > in practice someone is acting as though some other technology is > preferred. A genuine policy of preferring Ada, other things being > equal, might well be preferable. For example, this would mean that > hardware supporting Ada should be preferred over hardware that > does not support Ada. There is one Catch-22 I will be glad to get rid of. Right now on DoD programs, the "kiss of death" for the use of Ada or even the use of some hardware is the existance of an UNvalidated Ada compiler for that platform. The mandate says you can't use the unvalidated compiler, and a waiver is difficult if not impossible to get because there is an Ada compiler (usually with a lapsed validation). There are also projects where a validation or three is essentially a negligible cost compared to the risk avoided. (I've worked on a couple.) We need a policy to deal with both. -- Robert I. Eachus with Standard_Disclaimer; use Standard_Disclaimer; function Message (Text: in Clever_Ideas) return Better_Ideas is...