Subject: Re: [linux-audio-dev] Article about multithreading
From: Joe Pfeiffer (pfeiffer_AT_cs.nmsu.edu)
Date: Tue Jun 19 2001 - 23:31:37 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.
Good point. However, if type-checking took the kind of run-time
effort that deadlock avoidance does, it would become arguable that it
was indeed misplaced effort. Whether or not garbage collection is
misplaced effort is a religious debate.
-- Joseph J. Pfeiffer, Jr., Ph.D. Phone -- (505) 646-1605 Department of Computer Science FAX -- (505) 646-1002 New Mexico State University http://www.cs.nmsu.edu/~pfeiffer SWNMRSEF: http://www.nmsu.edu/~scifair
This archive was generated by hypermail 2b28 : Tue Jun 19 2001 - 23:30:54 EEST