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: 108abf,d3bcc180a8b0eea4 X-Google-Attributes: gid108abf,public X-Google-Thread: 103376,d3bcc180a8b0eea4 X-Google-Attributes: gid103376,public From: "jtarver" Subject: Re: [Fwd: F22 completes 11% of its Flight tests] Date: 2000/01/12 Message-ID: #1/1 X-Deja-AN: 571742524 References: <387C8859.621FA20B@netscape.net> <387CC1C0.4C57E34C@quadruscorp.com> X-Priority: 3 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Trace: 2-00178123c1ebef45d0836c94a54cf0b34630ca91cf614aaf8176 X-MSMail-Priority: Normal NNTP-Posting-Date: Wed, 12 Jan 2000 13:42:23 EST Newsgroups: comp.lang.ada,rec.aviation.military Date: 2000-01-12T00:00:00+00:00 List-Id: Marin D. Condic wrote in message news:387CC1C0.4C57E34C@quadruscorp.com... > > > > It will be highly impressive to see a version of Ada that is actually > > transportable. The first thing the development of Ada compilers did was > > allow extensions in direct violation of the charter for the system. This > > worked to deliver the pork to Boston, but really comprimised the intent of > > the DARPA program funding Ada. > > > > John > > I worked F22 engine control software written in Ada for years - and may > yet again someday. We were having a similar problem with respect to the > M68040 becoming obsolete and needing to be replaced (probably by the > PowerPC) as the engine goes into production. I'll throw my $0.02 worth > in: > > There is not now, nor has there ever been, *any* computer language that > is 100% portable. *Especially* in the field of embedded computers. So > when portability comes up, you have to ask the question as a matter of > degree. "It all depends", as they say. > Ada is the most portable language I have ever worked with. I have > dragged large chunks of Ada code out of an embedded environment and > compiled it with zero modifications on a Sun workstation and on a PC and > had it run just as it did in the embedded box. I have had very similar > experiences with a large number of other bodies of code (non-embedded) > so I don't think this was unique. Ada was originally envisioned to be platform transparent. When Data General produced the only 100% compliant compliler and the Ada development program went for the noncompliant VAX as their standard platform that idea was out the window. > The trick with programming long lived embedded computers is knowing how > to isolate the things which are going to be processor/system specific. > That way, when you have to upgrade to new hardware, the problem isn't as > horrific. The biggest problem is that changing anything in the box means > you have to go through huge amounts of revalidation of the system, and > this is an issue independent of the processor or language you choose to > use. Ada has always been a big help in enhancing portability, but it can > never solve all of the problems. No language can. Well you know I'd like to argue with you, but there is little in what you wrote to dispute. John