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=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!mailrus!ames!pasteur!ucbvax!AJPO.SEI.CMU.EDU!rracine
From: rracine@AJPO.SEI.CMU.EDU
Newsgroups: comp.lang.ada
Subject: Real-time UNIX(registered trademark of AT&T)
Message-ID: <8808291317.AA22199@ajpo.sei.cmu.edu>
Date: 29 Aug 88 13:17:17 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
List-Id: <comp.lang.ada>

Fred Hosch asks:
>I would appreciate any information on developing real-time systems with
>Ada in a unix environment. Thanks.

It all depends on what you call real-time.  MASSCOMP guarantees an interrupt
response time of 8 milliseconds.  For some applications, that is fine.  For
an airplane control system trying to run every 10 milliseconds, that is
considerably too much overhead.  And considering the number of people who
do not use Ada tasking because they cannot afford 100 microseconds for a
rendezvous, 8 milliseconds is not likely to be acceptable.

This is, by the way, not an Ada issue.  General purpose operating systems
have too much to do to be able to give users quick response.  

The IEEE POSIX standard folks are working on a "real-time" interface, based
on work by AT&T, MASSCOMP and others.  Getting implementations which
deliver the performance allowed by the interface might take a while, though.

Roger Racine
C.S. Draper Laboratory
rracine@ajpo.sei.cmu.edu
(617) 258-2489