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.6 required=5.0 tests=BAYES_20,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,567f87f476bd8e1c
X-Google-Attributes: gid103376,public
From: griest-tom@cs.yale.edu (Tom Griest)
Subject: Re: Tips for realtime embedded Ada?
Date: 1996/04/16
Message-ID: <4l0d59INN2na@RA.DEPT.CS.YALE.EDU>#1/1
X-Deja-AN: 147795454
distribution: world
references: <4ku9jf$b7u@hacgate2.hac.com>
organization: Yale University Computer Science Dept., New Haven, CT 06520-2158
cc: jpgluth@ccgate.hac.com
newsgroups: comp.lang.ada
Date: 1996-04-16T00:00:00+00:00
List-Id: <comp.lang.ada>

John Gluth <jpGluth@ccgate.hac.com> writes:

>I'm looking for wisdom regarding designing software for a realtime
>embedded application.
>
>Can you suggest constructs, design philosophies, etc. to use/avoid
>to avoid inefficient code?

If you have the flexibility to use Ada95, take a look at the real-time 
annex.  In genneral, you want to avoid a design that results in very
large numbers of simultaneous tasks unless you have parallel hardware
which takes advantage of the parallelism.

The Keep It Simple philosophy is usually best for real-time.  Add
complexity only when it buys you a big win in requirements relief.
For example, you might add timestamping and extrapolation if it
relaxes the requirement on sampling period stability and therefore
becomes more tolerant of interrupt jitter.

A netnews article is not the best place to go into all the details,
and that's why there are several books on this subject.  I can
recommend books by either Andy Wellings or Alan Burns, but I'm sure
there are many other good books out there too.

-Tom