From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Marius Vollmer Newsgroups: gmane.lisp.guile.user,gmane.lisp.guile.devel Subject: Re: About cleaning up the thread stuff Date: Wed, 19 Jan 2005 00:05:20 +0100 Message-ID: <87zmz6l4nj.fsf@zagadka.de> References: <87k6qawg36.fsf@zip.com.au> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1106090400 7883 80.91.229.6 (18 Jan 2005 23:20:00 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 18 Jan 2005 23:20:00 +0000 (UTC) Cc: guile-devel@gnu.org Original-X-From: guile-user-bounces+guile-user=m.gmane.org@gnu.org Wed Jan 19 00:19:50 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1Cr2dZ-0007yP-00 for ; Wed, 19 Jan 2005 00:19:49 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Cr2pU-00084K-2t for guile-user@m.gmane.org; Tue, 18 Jan 2005 18:32:08 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Cr2ow-0007yq-4q for guile-user@gnu.org; Tue, 18 Jan 2005 18:31:34 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Cr2op-0007wV-T8 for guile-user@gnu.org; Tue, 18 Jan 2005 18:31:30 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Cr2om-0007nc-Vt for guile-user@gnu.org; Tue, 18 Jan 2005 18:31:26 -0500 Original-Received: from [199.232.41.8] (helo=mx20.gnu.org) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1Cr2Sg-00017N-Rx for guile-user@gnu.org; Tue, 18 Jan 2005 18:08:34 -0500 Original-Received: from [195.253.8.218] (helo=mail.dokom.net) by mx20.gnu.org with esmtp (Exim 4.34) id 1Cr2Pb-0000Ag-Pg for guile-user@gnu.org; Tue, 18 Jan 2005 18:05:23 -0500 Original-Received: from [195.138.43.11] (helo=zagadka.ping.de) by mail.dokom.net with smtp (Exim 4.34) id 1Cr2PZ-0007yb-Rg for guile-user@gnu.org; Wed, 19 Jan 2005 00:05:22 +0100 Original-Received: (qmail 11249 invoked by uid 1000); 18 Jan 2005 23:05:20 -0000 Original-To: guile-user@gnu.org In-Reply-To: <87k6qawg36.fsf@zip.com.au> (Kevin Ryde's message of "Wed, 19 Jan 2005 09:02:53 +1100") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/21.3.50 (gnu/linux) X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: guile-user-bounces+guile-user=m.gmane.org@gnu.org Errors-To: guile-user-bounces+guile-user=m.gmane.org@gnu.org Xref: main.gmane.org gmane.lisp.guile.user:4112 gmane.lisp.guile.devel:4702 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.devel:4702 Kevin Ryde writes: > Marius Vollmer writes: >> >> dead-locks might be detected > > I wouldn't worry about that. I think the combinations of things a > thread can block on will make it too hard to be sure a deadlock is > occurring. There might even be some weird apparent deadlock that's > meant to be broken by a signal handler cancelling one thread or > something. Yes, true. Maybe the debugger could still try to figure out whether there is a dead-lock, or the program could explicitely ask for it. Etc. >> mutexes can be recursive > > Yep, I think that's friendliest. I think there is use for both kinds of mutexes. Sometimes you want a recursive one, sometimes locking twice from the same thread is an error. -- GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405 _______________________________________________ Guile-user mailing list Guile-user@gnu.org http://lists.gnu.org/mailman/listinfo/guile-user