Date: Sun, 16 Mar 2003 12:56:31 -0500 (EST) From: Daniel Eischen <eischen@pcnet1.pcnet.com> To: Darren Reed <darrenr@reed.wattle.id.au> Cc: David Xu <davidxu@FreeBSD.org>, John Baldwin <jhb@FreeBSD.org>, cvs-all@FreeBSD.org, cvs-src@FreeBSD.org, src-committers@FreeBSD.org Subject: Re: cvs commit: src/lib/libpthread/thread thr_rwlock.c Message-ID: <Pine.GSO.4.10.10303161254440.20728-100000@pcnet1.pcnet.com> In-Reply-To: <200303161608.DAA02164@avalon.reed.wattle.id.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 17 Mar 2003, Darren Reed wrote: > So what you're saying is this design prevents bad code being written. > And the problem is ? I agree :-) But unfortunately POSIX allows a thread to recursively take a read lock on a rwlock_t. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10303161254440.20728-100000>