comp.lang.ada
 help / color / mirror / Atom feed
From: l107353@cliffy.lfwc.lockheed.com (Garlington KE)
Subject: Re: DoD Ada 95 Policy
Date: 1995/03/29
Date: 1995-03-29T00:00:00+00:00	[thread overview]
Message-ID: <3lcei9$a84@butch.lmsc.lockheed.com> (raw)
In-Reply-To: D67Juq.Hw8@inmet.camb.inmet.com

Tucker Taft (stt@spock.camb.inmet.com) wrote:
: It looks like most DoD programs can start using Ada 95 compilers, so long
: as they are willing to take on and manage the increased risk, and so long
: as they will deliver with a validated Ada 95 compiler.

This is true. However, if your contract explicitly calls out MIL-STD-1815
(as the F-22 contract doesn, for example), you still have to do something
contract-wise to use Ada 95, either a spec change or a spec waiver of some
type, Paige's memo was guidance to the services; it doesn't override the
language of your contract.

Also, there's not a lot of guidance out there right now on what it means to
"manage the increased risk," so this is something you have to work with your
customer.

--------------------------------------------------------------------
Ken Garlington                  GarlingtonKE@lfwc.lockheed.com
F-22 Computer Resources         Lockheed Fort Worth Co.

If LFWC or the F-22 program has any opinions, they aren't telling me.




      reply	other threads:[~1995-03-29  0:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-03-28 13:17 DoD Ada 95 Policy Jim Vijay
1995-03-29  0:00 ` Tucker Taft
1995-03-29  0:00   ` Garlington KE [this message]
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox