From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Christopher Cramer Newsgroups: gmane.lisp.guile.devel Subject: future thread interface Date: Tue, 1 Jul 2003 01:32:50 -0500 Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Message-ID: <20030701013250.A12964@kiwi.pyrotechnics.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1057040935 26969 80.91.224.249 (1 Jul 2003 06:28:55 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Tue, 1 Jul 2003 06:28:55 +0000 (UTC) Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Tue Jul 01 08:28:54 2003 Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19XEdK-00070p-00 for ; Tue, 01 Jul 2003 08:28:54 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.20) id 19XEdg-0000iy-8y for guile-devel@m.gmane.org; Tue, 01 Jul 2003 02:29:16 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20) id 19XEcy-0008KK-Tk for guile-devel@gnu.org; Tue, 01 Jul 2003 02:28:32 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20) id 19XEcm-0007vg-7V for guile-devel@gnu.org; Tue, 01 Jul 2003 02:28:21 -0400 Original-Received: from pyro.net ([207.7.10.6] helo=kiwi.pyro.net) by monty-python.gnu.org with smtp (Exim 4.20) id 19XEcj-0007rZ-Pn for guile-devel@gnu.org; Tue, 01 Jul 2003 02:28:17 -0400 Original-Received: (qmail 16089 invoked by uid 8610); 1 Jul 2003 06:32:50 -0000 Original-To: guile-devel@gnu.org Mail-Followup-To: guile-devel@gnu.org Content-Disposition: inline User-Agent: Mutt/1.2.5i X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Developers list for Guile, the GNU extensibility library List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: main.gmane.org gmane.lisp.guile.devel:2584 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.devel:2584 I have a few questions about where Guile is heading wrt to threads. 1. The goal is to be able to pick between different thread implementations. When is this choice actually supposed to be made: compile time, link time, during Guile startup, or when? Right now (looking at CVS) it's compile time, but it looks like the goal is during Guile startup; It just doesn't seem to be stated anywhere. 2. The prevailing view is apparently that at some point in time coop thread support will be completely dropped. When is this going to happen? Personally I would like to keep using coop threads until pthreads on Linux/glibc gets much more efficient than it is now. I don't use Guile on any multiprocessor systems, but I expect that eventually the efficiency problems will be small enough to be outweighed by the relative simplicity of pthreads. 3. A while ago I was working on a patch to eliminate all the blocking caused by accept/connect/etc. If I finish it now, can it possibly included in 1.6.5 (or in 1.6.x at all), or should I target the patch for 1.7? -- Christopher Cramer "People said it couldn't be that our soldiers would do such things. Now you read worse things in the mainstream media and people don't care. We used to say that if only people know about it, it would stop. Now they know about it, and it hasn't stopped." - Adam Keller _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://mail.gnu.org/mailman/listinfo/guile-devel