From: "Jeffrey R. Carter" <spam.jrcarter.not@nospam.acm.org>
Subject: Re: Interrupt handler and Ada.Real_Time.Timing_Events
Date: Sat, 16 May 2009 00:38:54 GMT
Date: 2009-05-16T00:38:54+00:00 [thread overview]
Message-ID: <yWnPl.700199$yE1.365158@attbi_s21> (raw)
In-Reply-To: <4A0E06E6.4000209@codelabs.ch>
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.
--
Jeff Carter
"From this day on, the official language of San Marcos will be Swedish."
Bananas
28
next prev parent reply other threads:[~2009-05-16 0:38 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 [this message]
2009-05-29 15:59 ` Reto Buerki
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