From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chris Vine Newsgroups: gmane.lisp.guile.user Subject: Re: libguile thread safety Date: Tue, 18 Mar 2014 10:49:04 +0000 Message-ID: <20140318104904.69e75af7@bother.homenet> References: <20140103233407.36382e5f@bother.homenet> <8738l41p8r.fsf@netris.org> <20140104124459.6c604ae1@bother.homenet> <87y52vzgfc.fsf@netris.org> <20140104210118.3564073f@bother.homenet> <20140104233120.77b0edaa@bother.homenet> <87k3eexrc6.fsf@netris.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1395139755 25553 80.91.229.3 (18 Mar 2014 10:49:15 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 18 Mar 2014 10:49:15 +0000 (UTC) Cc: guile-user@gnu.org To: Mark H Weaver Original-X-From: guile-user-bounces+guile-user=m.gmane.org@gnu.org Tue Mar 18 11:49:24 2014 Return-path: Envelope-to: guile-user@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WPraF-0003CX-Op for guile-user@m.gmane.org; Tue, 18 Mar 2014 11:49:23 +0100 Original-Received: from localhost ([::1]:34446 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPraF-0005Ut-Fi for guile-user@m.gmane.org; Tue, 18 Mar 2014 06:49:23 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:53879) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPra1-0005Uf-49 for guile-user@gnu.org; Tue, 18 Mar 2014 06:49:15 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WPrZr-00054y-96 for guile-user@gnu.org; Tue, 18 Mar 2014 06:49:09 -0400 Original-Received: from smtpout1.wanadoo.co.uk ([80.12.242.29]:59792 helo=smtpout.wanadoo.co.uk) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPrZr-00054W-2S for guile-user@gnu.org; Tue, 18 Mar 2014 06:48:59 -0400 Original-Received: from bother.homenet ([95.146.112.126]) by mwinf5d09 with ME id eyov1n00d2jgrrz03yowro; Tue, 18 Mar 2014 11:48:56 +0100 Original-Received: from bother.homenet (localhost [127.0.0.1]) by bother.homenet (Postfix) with ESMTP id 684C98855B; Tue, 18 Mar 2014 10:49:04 +0000 (GMT) In-Reply-To: <87k3eexrc6.fsf@netris.org> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.22; i686-pc-linux-gnu) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 80.12.242.29 X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-user-bounces+guile-user=m.gmane.org@gnu.org Original-Sender: guile-user-bounces+guile-user=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.user:11125 Archived-At: On Sun, 05 Jan 2014 12:37:29 -0500 Mark H Weaver wrote: [snip] > This wouldn't work. First of all, 'use-modules' is a macro, not a > procedure, but more importantly, modules are autoloaded in many places > deep in the guts of the system. Notice that Chris' test cases didn't > use 'use-modules' at all. In fact, a module is autoloaded the first > time 'scm_c_eval_string' is called. Also, there are potential > deadlocks. > > We should just fix the problem properly, and that's what I intend to > do. I notice that the thread-safe initialization of guile by scm_with_guile() seems to have been fixed in guile-2.0.10, but the loading of modules remains not thread-safe. Has thread-safe module loading turned out to be too difficult to do, or is it still something that is likely to happen in the future? Chris