Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!news.linkpendium.com!news.linkpendium.com!newsfeeds.ihug.co.nz!lust.ihug.co.nz!ihug.co.nz!not-for-mail From: Lawrence D'Oliveiro Newsgroups: comp.lang.java.programmer Subject: Re: Making one or more threads wait for another to produce a value or fail Followup-To: comp.lang.java.programmer Date: Wed, 01 Jun 2011 16:40:28 +1200 Organization: Geek Central Lines: 11 Message-ID: References: NNTP-Posting-Host: 118-92-86-36.dsl.dyn.ihug.co.nz Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8Bit X-Trace: lust.ihug.co.nz 1306903228 4410 118.92.86.36 (1 Jun 2011 04:40:28 GMT) X-Complaints-To: abuse@ihug.co.nz NNTP-Posting-Date: Wed, 1 Jun 2011 04:40:28 +0000 (UTC) User-Agent: KNode/4.4.11 Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:4844 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.) Or, going further back, Occam (based on Hoare’s CSP)?