comp.lang.ada
 help / color / mirror / Atom feed
From: "Pat Rogers" <progers@classwide.com>
Subject: Re: Are rendezvous dead?
Date: Sun, 14 Apr 2002 14:00:56 GMT
Date: 2002-04-14T14:00:56+00:00	[thread overview]
Message-ID: <sYfu8.157$h24.105729203@newssvr11.news.prodigy.com> (raw)
In-Reply-To: 3CB940F7.4EC50CFD@yahoo.com

"Anatoly Chernyshev" <rhezusfactor@yahoo.com> wrote in message
news:3CB940F7.4EC50CFD@yahoo.com...
> I remember, a long time ago I did read a paper entitled like "Rendezvous
> are dead. Long live protected object" where it was stated that protected
> types are much more convenient for communication between tasks than
> rendezvous. And also the rationale dwells mostly upon these types, not
> rendezvous.
> The question is: are there any practical instances (in Ada 95) when use
> of rendezvous is more advantageous than of protected types? In other
> words, is it worhty of trying to write the code using only protected
> types and completely ignoring rendezvous as possible solution (like the
> GOTO operator)?


If tasks require _direct_ communication/synchronization, rendezvous is generally
the right way to go for that specific part of their behavior.  Otherwise,
protected objects are preferable.


--
---
Patrick Rogers                       Consulting and Training in:
http://www.classwide.com          Real-Time/OO Languages
progers@classwide.com               Hard Deadline Schedulability Analysis
(281)648-3165                                 Software Fault Tolerance





  parent reply	other threads:[~2002-04-14 14:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-14  8:42 Are rendezvous dead? Anatoly Chernyshev
2002-04-14 10:55 ` Dmitry A.Kazakov
2002-04-14 14:00 ` Pat Rogers [this message]
2002-04-15 13:38   ` Marin David Condic
2002-04-14 19:52 ` Robert Dewar
2002-04-16  8:48   ` John McCabe
2002-04-15 14:04 ` Ted Dennison
2002-04-15 16:09   ` Jim Rogers
2002-04-15 16:36     ` Jean-Pierre Rosen
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox