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 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: a07f3367d7,e69505d5161d7d41
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news3.google.com!feeder.news-service.com!feeder.news-service.com!feeder.motzarella.org!news.motzarella.org!news.eternal-september.org!not-for-mail
From: Reto Buerki <reet@codelabs.ch>
Newsgroups: comp.lang.ada
Subject: Re: Interrupt handler and Ada.Real_Time.Timing_Events
Date: Fri, 29 May 2009 17:59:46 +0200
Organization: A noiseless patient Spider
Message-ID: <4A200672.8030906@codelabs.ch>
References: <guk532$u44$1@news.motzarella.org>
 <d963de18-83f6-4f92-a30b-39b7f9dfc4d3@r34g2000vbi.googlegroups.com>
 <4A0E06E6.4000209@codelabs.ch> <yWnPl.700199$yE1.365158@attbi_s21>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Trace: news.eternal-september.org
 U2FsdGVkX1/iRUe92x6msVG2dg3rP4s+S0+z3b9toqB4Jn9XJ0UtmfOppMuL4QeCantcqecFLQIhlKgmD3F80lZvbiN3SGCbSzSAN6xgdusRG8TJ9Pxfiz7DxuVpwCQFAwSjgMWda4w=
X-Complaints-To: abuse@eternal-september.org
NNTP-Posting-Date: Fri, 29 May 2009 15:59:45 +0000 (UTC)
In-Reply-To: <yWnPl.700199$yE1.365158@attbi_s21>
X-Auth-Sender: U2FsdGVkX1+ogcg1ceIiAJc7oz3GI77Lz8u33uJe3xg=
Cancel-Lock: sha1:Eztye84waxIXQpWPN8ktB/0QR00=
User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103)
Xref: g2news2.google.com comp.lang.ada:6105
Date: 2009-05-29T17:59:46+02:00
List-Id: <comp.lang.ada>

Jeffrey R. Carter wrote:
> Reto Buerki wrote:
>>
>> We are using Ada.Real_Time.Timing_Events to implement an event-driven
>> architecture in our application. The Timing_Event type seemed perfect
>> for this.
> 
> Timing_Events are certainly suited for this. However, they were added in
> the most recent revision of the language. Event-driven systems were
> implemented in Ada long before that revision. Should you be unable to
> get your application to work with Timing_Events, you can use the
> old-fashioned way to achieve the same thing. This is done by having
> tasks that execute delay statements and then call the appropriate
> protected operations. Effectively, a Timing_Event object is shorthand
> for such a task.

Thanks for your answer. Re-implementing the Timing_Events functionality
seems to be the only possible solution for the moment.

I sent a bug report about this issue to report@adacore.com and added it
to the GCC bug database (bug #40285).