From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.5-pre1
Date: 16 Oct 92 20:45:20 GMT
From: cis.ohio-state.edu!news.sei.cmu.edu!ajpo.sei.cmu.edu!griest@ucbvax.Berkel
ey.EDU  (Tom Griest)
Subject: Re: Ada and real-time
Message-ID: <1992Oct16.204520.18405@sei.cmu.edu>
List-Id: <comp.lang.ada>

In article <1992Oct15.163026.7899@saifr00.cfsat.honeywell.com> walls@saifr00.cf
sat.honeywell.com (Gerald Walls) writes:
>In article <1992Oct15.144135.24045@sei.cmu.edu> jbg@sei.cmu.edu (John Goodenou
gh) writes:
>>
>>By "non-deterministic tasking" do you mean the fact that it can be difficult
>>or impossible to write down a timeline for a set of Ada tasks, given
>>variations in execution times and the effect of preemption?  If so, this is
>>not, in itself, sufficient reason to conclude that Ada tasking is unsuitable
>>for embedded real-time systems.  
>>
>
>the FAA requires this in avionics software.  Ada tasking is not
>suitable for real-time avionics software.


Show me the regulation that prohibits "this".  I know of commercial
avionics software that does not have purely deterministic scheduling.
(Any software that has asynchonous interrupts probably fits into
this category.)

   Tom Griest