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: 103376,1356f4179c1e4ef4
X-Google-Attributes: gid103376,public
From: Ken Garlington <garlingtonke@lmtas.lmco.com>
Subject: Re: ADA task
Date: 1996/09/14
Message-ID: <323AC0F0.758A@lmtas.lmco.com>#1/1
X-Deja-AN: 180626232
references: <5174qu$o1p@nr1.ottawa.istar.net>
 <51cjp0$q7k@watnews1.watson.ibm.com>
content-type: text/plain; charset=us-ascii
organization: Lockheed Martin Tactical Aircraft Systems
mime-version: 1.0
newsgroups: comp.lang.ada
x-mailer: Mozilla 2.02 (Macintosh; I; 68K)
Date: 1996-09-14T00:00:00+00:00
List-Id: <comp.lang.ada>


Norman H. Cohen wrote:
> 
> In article <5174qu$o1p@nr1.ottawa.istar.net>, "Roumen Roupski"
> <Roumen.Roupski@Pika.Ca> writes:
> 
> |> 1. How can I implement a task running at regular intervals, for example
> |> every 50ms +/- 5ms. The task activation must be guaranteed too.
> 

[answer deleted]

I assume by the last sentence in the original question - "The task activation must 
be guaranteed too." - that some discussion of priorities and/or how to connect a 
task to a hardware interrupt or other aperiodic event is also needed. Anyone want to 
post an expanded answer?

> 
> --
> Norman H. Cohen    ncohen@watson.ibm.com

-- 
LMTAS - "Our Brand Means Quality"