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.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Thread: 103376,470e89e7a6575920
X-Google-Attributes: gid103376,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news2.google.com!news1.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!t-online.de!newsfeed-0.progon.net!progon.net!news.mediascape.de!zen.net.uk!demorgan.zen.co.uk!peer1.news.newnet.co.uk!194.159.246.34.MISMATCH!peer-uk.news.demon.net!kibo.news.demon.net!mutlu.news.demon.net!news.demon.co.uk!demon!not-for-mail
From: Simon Wright <simon.j.wright@mac.com>
Newsgroups: comp.lang.ada
Subject: Re: Periodic tasks - organization
Date: Wed, 16 Jul 2008 22:38:51 +0100
Organization: Pushface
Message-ID: <m2iqv5ecgk.fsf@mac.com>
References: 
 <86589099-2e4e-4b7d-ace0-6f1f864a3fa2@y21g2000hsf.googlegroups.com>
 <6e0jbhF4o43oU1@mid.individual.net>
 <561c8fa7-f26d-49a3-b54c-229c20462c04@r66g2000hsg.googlegroups.com>
NNTP-Posting-Host: pogner.demon.co.uk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: news.demon.co.uk 1216244332 8480 62.49.19.209 (16 Jul 2008 21:38:52
 GMT)
X-Complaints-To: abuse@demon.net
NNTP-Posting-Date: Wed, 16 Jul 2008 21:38:52 +0000 (UTC)
Cancel-Lock: sha1:nYta7etKknyw48o7ujxeUYTF3DQ=
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (darwin)
Xref: g2news1.google.com comp.lang.ada:1180
Date: 2008-07-16T22:38:51+01:00
List-Id: <comp.lang.ada>

Anh Vo <anhvofrcaus@gmail.com> writes:

> It is even better to use periodic timers built on top
> Ada.Real_Time.Timing_Events. Then, explicit tasks are not needed.

Only 'better' if that solution meets a need that's not met by the
straightforward approach.

I see that Timing Event Handlers are meant to be executed directly by
the protected handler operation
(http://www.adaic.com/standards/05rm/html/RM-D-15.html 25/2), so
clearly the intent is that some task should be released by the action
of the handler (similar to interrupts). So you still need explicit
tasks! just replacing a delay with a blocking wait on the PO which
will be triggered by the timing event -- a lot of complication.