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: 11035d,b65739503d72f172
X-Google-Attributes: gid11035d,public
X-Google-Thread: 103376,b65739503d72f172
X-Google-Attributes: gid103376,public
From: Matthew Heaney <matthew_heaney@acm.org>
Subject: Re: Timers in application
Date: 1999/06/08
Message-ID: <m3d7z6fyzb.fsf@mheaney.ni.net>#1/1
X-Deja-AN: 487119008
References: <375D1E02.8F1C0D6E@res.raytheon.com>
NNTP-Posting-Date: Tue, 08 Jun 1999 09:11:47 PDT
Newsgroups: comp.unix.solaris,comp.lang.ada
Date: 1999-06-08T00:00:00+00:00
List-Id: <comp.lang.ada>

On 08 Jun 1999 06:43:30 -0700, askeya <askeya@res.raytheon.com> wrote:

> I am developing a Solaris 2.6 application (Ada95 with Apex) that needs a
> timer service that allows me to schedule multiple simultaneous wakeups. 
> I have looked at "setitimer" and "alarm" man pages, but these services
> appear to only allow one timer per process and/or thread.  Is this
> correct?

What's wrong with using "delay until"?  The whole point of Ada run-time
is that you don't have to muck with OS calls.