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: Fri, 20 Feb 2004 22:26:48 -0500 Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Message-ID: References: <87znbdi85m.fsf@zip.com.au> 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 1077334133 12061 80.91.224.253 (21 Feb 2004 03:28:53 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 21 Feb 2004 03:28:53 +0000 (UTC) Cc: djurfeldt@nada.kth.se Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Sat Feb 21 04:28:49 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 1AuNov-0005CV-00 for ; Sat, 21 Feb 2004 04:28:49 +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 1AuNoi-0001E9-Sh for guile-devel@m.gmane.org; Fri, 20 Feb 2004 22:28:36 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1AuNno-0000ua-SH for guile-devel@gnu.org; Fri, 20 Feb 2004 22:27:40 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1AuNnB-0008FF-NP for guile-devel@gnu.org; Fri, 20 Feb 2004 22:27:39 -0500 Original-Received: from [213.212.20.77] (helo=kvast.blakulla.net) by monty-python.gnu.org with esmtp (Exim 4.30) id 1AuNn2-0007t3-FL for guile-devel@gnu.org; Fri, 20 Feb 2004 22:26:52 -0500 Original-Received: from witch ([209.150.45.158]) by kvast.blakulla.net with esmtp (Exim 3.36 #1 (Debian)) id 1AuNmz-0005NF-00; Sat, 21 Feb 2004 04:26:49 +0100 Original-Received: from mdj by witch with local (Exim 3.35 #1 (Debian)) id 1AuNmy-0001XM-00; Fri, 20 Feb 2004 22:26:48 -0500 Original-To: guile-devel@gnu.org, mvo@zagadka.ping.de In-Reply-To: (Mikael Djurfeldt's message of "Fri, 20 Feb 2004 22:24:37 -0500") 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:3420 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.devel:3420 Mikael Djurfeldt writes: > So, the policy needs to specify where the border between Guile and > user responsibility goes. In most cases, I would probably draw the > line so that as much as possible of the responsibility is left to the > user with the exceptions that 1. Guile should never segfault due to > misuse in this respect, and, 2. Guile need to have enough thread > safety so that it's reasonably convenient to write parallel programs. BTW, applying this policy on crypt probably means that we shouldn't protect it with a mutex. M _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://mail.gnu.org/mailman/listinfo/guile-devel