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 14:55:23 -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 1077566426 19239 80.91.224.253 (23 Feb 2004 20:00:26 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 23 Feb 2004 20:00:26 +0000 (UTC) Cc: djurfeldt@nada.kth.se, guile-devel@gnu.org, Marius Vollmer Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Mon Feb 23 21:00:05 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 1AvMFJ-0002c6-00 for ; Mon, 23 Feb 2004 21:00:05 +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 1AvMCX-0001ex-Jj for guile-devel@m.gmane.org; Mon, 23 Feb 2004 14:57:13 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1AvMCC-0001en-1O for guile-devel@gnu.org; Mon, 23 Feb 2004 14:56:52 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1AvMBg-0001ah-BH for guile-devel@gnu.org; Mon, 23 Feb 2004 14:56:51 -0500 Original-Received: from [213.212.20.77] (helo=kvast.blakulla.net) by monty-python.gnu.org with esmtp (Exim 4.30) id 1AvMBg-0001ac-2t for guile-devel@gnu.org; Mon, 23 Feb 2004 14:56:20 -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 1AvMAm-0004E5-00; Mon, 23 Feb 2004 20:55:24 +0100 Original-Received: from mdj by chunk with local (Exim 4.30) id 1AvMAl-0006WP-PR; Mon, 23 Feb 2004 14:55:23 -0500 Original-To: djurfeldt@nada.kth.se In-Reply-To: (Mikael Djurfeldt's message of "Mon, 23 Feb 2004 14:46:50 -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:3436 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.devel:3436 Mikael Djurfeldt writes: > Marius Vollmer writes: > >>> 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. >> >> Yes, exactly my view. Also, I would broaden point 1 a bit: we should >> also 'fix' functions that can not every be used in a threaded program >> without mutexes around them. Like libc getpwent. They might not >> segfault, but you can't use them anyway in a threaded program. > > But the normal case is *not* a threaded program. The everyday program > can use crypt with a static buffer without mutexes. A *threaded* > program needs mutexes... > > This is why I'm leaning towards a minimal policy---to design for the > common case of non-threaded programs, but leave the possibility open > to write parallel code without too much difficulty. Of course: If you by 'fix' mean making functions reentrant (that is: fixes without too much overhead), then I would agree. M _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://mail.gnu.org/mailman/listinfo/guile-devel