Subject: Re: [linux-audio-dev] Article about multithreading
From: John Regehr (regehr_AT_cs.utah.edu)
Date: Mon Jun 18 2001 - 20:52:39 EEST
On Sun, 17 Jun 2001, Joe Pfeiffer wrote:
> mutex might conceivably lead to a deadlock eventually). Deadlock is
> really programmer error, so trying to avoid it is a really misplaced
> effort.
The conclusion "trying to avoid deadlock is misplaced effort" does not
follow from "deadlock is programmer error". If it did, then
"type-checking is misplaced effort", "garbage collection is misplaced
effort", and a whole lot of other ridiculous conclusions would also
follow from the analogous statements.
John
This archive was generated by hypermail 2b28 : Mon Jun 18 2001 - 20:51:16 EEST