From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Mikael Djurfeldt Newsgroups: gmane.lisp.guile.devel Subject: Re: crypt mutex Date: Mon, 23 Feb 2004 15:01:09 -0500 Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Message-ID: References: <87znbdi85m.fsf@zip.com.au> <87znb98v9x.fsf@zagadka.ping.de> Reply-To: djurfeldt@nada.kth.se NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1077567399 22471 80.91.224.253 (23 Feb 2004 20:16:39 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 23 Feb 2004 20:16:39 +0000 (UTC) Cc: djurfeldt@nada.kth.se, guile-devel@gnu.org Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Mon Feb 23 21:16:25 2004 Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AvMV7-0004J0-00 for ; Mon, 23 Feb 2004 21:16:25 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.30) id 1AvMTz-0008Fk-GY for guile-devel@m.gmane.org; Mon, 23 Feb 2004 15:15:15 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1AvMTV-0008E2-7B for guile-devel@gnu.org; Mon, 23 Feb 2004 15:14:45 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1AvMSy-00085P-7W for guile-devel@gnu.org; Mon, 23 Feb 2004 15:14:44 -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.30) id 1AvMSx-00085M-VY for guile-devel@gnu.org; Mon, 23 Feb 2004 15:14:12 -0500 Original-Received: from [213.212.20.77] (helo=kvast.blakulla.net) by mx20.gnu.org with esmtp (Exim 4.30) id 1AvMGP-00078u-DC for guile-devel@gnu.org; Mon, 23 Feb 2004 15:01:13 -0500 Original-Received: from chunk.mit.edu ([18.42.2.92] helo=chunk ident=Debian-exim) by kvast.blakulla.net with esmtp (Exim 3.36 #1 (Debian)) id 1AvMGM-0004EX-00; Mon, 23 Feb 2004 21:01:10 +0100 Original-Received: from mdj by chunk with local (Exim 4.30) id 1AvMGL-0006WZ-TR; Mon, 23 Feb 2004 15:01:09 -0500 Original-To: Marius Vollmer In-Reply-To: <87znb98v9x.fsf@zagadka.ping.de> (Marius Vollmer's message of "Mon, 23 Feb 2004 20:12:42 +0100") User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux) X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Developers list for Guile, the GNU extensibility library List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: main.gmane.org gmane.lisp.guile.devel:3437 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.devel:3437 Marius Vollmer writes: > can lists be meaningfully made thread safe? Your general question is very relevant. Regarding this example, my answer would be that we should limit ourselves to making sure that we don't get segfault or memory corruption if multiple threads randomly mutates pairs. If a threaded program needs thread safe (in this case: mutually exclusive) access to a list data structure, it uses a mutex. M _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://mail.gnu.org/mailman/listinfo/guile-devel