Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: "John B. Matthews" Newsgroups: comp.lang.java.programmer Subject: Re: Making one or more threads wait for another to produce a value or fail Date: Wed, 01 Jun 2011 11:22:56 -0400 Organization: The Wasteland Lines: 28 Message-ID: References: NNTP-Posting-Host: LQJtZWzu+iKlBROuDg+IUg.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: abuse@aioe.org User-Agent: MT-NewsWatcher/3.5.3b3 (Intel Mac OS X) X-Notice: Filtered by postfilter v. 0.8.2 Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:4859 In article , Lawrence D'Oliveiro wrote: > In message , Peter > Duniho wrote: > > > The concurrency stuff in particular seems a bit haphazard to me in > > terms of what features it provides, but then I've found that to be > > true in any other concurrency API I've used ... > > How about Ada? (Considered robust and trustworthy enough to implement > the life-support system on the International Space Station.) Ada provides excellent high-level support for concurrency, but it too had to evolve [*]. Moreover, any particular implementation can be defective. In the present case, your Ada example was insightful; but without further elucidation, it may be seen as malapropos. > Or, going further back, Occam (based on Hoare’s CSP)? [*] -- John B. Matthews trashgod at gmail dot com