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.3 required=5.0 tests=BAYES_00,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII
Path: 
 g2news1.google.com!news4.google.com!feeder1-2.proxad.net!proxad.net!feeder2-2.proxad.net!newsfeed.arcor.de!newsspool1.arcor-online.net!news.arcor.de.POSTED!not-for-mail
From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Subject: Re: Periodic tasks - organization
Newsgroups: comp.lang.ada
User-Agent: 40tude_Dialog/2.0.15.1
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Reply-To: mailbox@dmitry-kazakov.de
Organization: cbb software GmbH
References: 
 <86589099-2e4e-4b7d-ace0-6f1f864a3fa2@y21g2000hsf.googlegroups.com>
  <6e0jbhF4o43oU1@mid.individual.net>
 <561c8fa7-f26d-49a3-b54c-229c20462c04@r66g2000hsg.googlegroups.com>
 <m2iqv5ecgk.fsf@mac.com>
 <e5e7d089-7e6d-4632-acbc-a81936ff489d@79g2000hsk.googlegroups.com>
 <m2ej5se29s.fsf@mac.com>
 <2172d1a7-39a7-412c-9f30-635054f9103d@q24g2000prf.googlegroups.com>
Date: Fri, 18 Jul 2008 18:22:52 +0200
Message-ID: <1jt6gtl169krz.1g52yb1id2u85$.dlg@40tude.net>
NNTP-Posting-Date: 18 Jul 2008 18:22:52 CEST
NNTP-Posting-Host: 15767a10.newsspool3.arcor-online.net
X-Trace: 
 DXC=28kH]NY7>;;^8FBo0_81f>McF=Q^Z^V384Fo<]lROoR18kF<OcfhCO;b5FMY:UF6[7[6LHn;2LCV>[<mhadbfdU;hnL`InSARn=V2PbDSBHVY4
X-Complaints-To: usenet-abuse@arcor.de
Xref: g2news1.google.com comp.lang.ada:1211
Date: 2008-07-18T18:22:52+02:00
List-Id: <comp.lang.ada>

On Fri, 18 Jul 2008 08:31:29 -0700 (PDT), Anh Vo wrote:

> On Jul 17, 12:31�pm, Simon Wright <simon.j.wri...@mac.com> wrote:

>> But there are limits on what is permissible within a protected
>> procedure, are there not?

[...]

> My design is completely different from yours. Indeed, an explicit task
> is not needed. See Gem #15, Timers, for details.
> http://www.adacore.com/2007/10/29/ada-gem-15/

Hmm, but it is exactly the design presented by Simon. The problem with it
is that the action fired upon a timer event is called from a protected
procedure.

This is IMO not what Maciej wanted, because as Simon has pointed out
protected procedures are very limited in what they allowed do and in how
they do it.

Another point is that even if that were the context of a task (which is
not), it still would be an unsatisfactory design, because simultaneously
triggered actions would block each other when overlapping.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de