From: Reto Buerki <reet@codelabs.ch>
Subject: Re: Interrupt handler and Ada.Real_Time.Timing_Events
Date: Fri, 29 May 2009 17:59:46 +0200
Date: 2009-05-29T17:59:46+02:00 [thread overview]
Message-ID: <4A200672.8030906@codelabs.ch> (raw)
In-Reply-To: <yWnPl.700199$yE1.365158@attbi_s21>
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).
next prev parent reply other threads:[~2009-05-29 15:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 16:26 Interrupt handler and Ada.Real_Time.Timing_Events Reto Buerki
2009-05-15 16:54 ` Adam Beneschan
2009-05-15 23:24 ` Reto Buerki
2009-05-15 16:56 ` Ludovic Brenta
2009-05-15 23:24 ` Hibou57 (Yannick Duchêne)
2009-05-16 0:20 ` Reto Buerki
2009-05-16 0:38 ` Jeffrey R. Carter
2009-05-29 15:59 ` Reto Buerki [this message]
2009-05-16 6:28 ` sjw
2009-05-16 11:05 ` Timing Example was " anon
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox