From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Marius Vollmer Newsgroups: gmane.lisp.guile.devel Subject: Re: problem with futures? Date: Sun, 29 Jan 2006 20:44:51 +0200 Message-ID: <873bj6g9gc.fsf@zagadka.de> References: <1135203013.4312.40.camel@localhost.localdomain> <66e540fe0512220156s47532d1co5841d7eef2e898de@mail.gmail.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1138560650 5450 80.91.229.2 (29 Jan 2006 18:50:50 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 29 Jan 2006 18:50:50 +0000 (UTC) Cc: guile-devel@gnu.org Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Sun Jan 29 19:50:47 2006 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1F3Hcj-00013W-Iy for guile-devel@m.gmane.org; Sun, 29 Jan 2006 19:50:07 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F3Hfb-0006ud-FS for guile-devel@m.gmane.org; Sun, 29 Jan 2006 13:53:03 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1F3Hap-0003fD-NQ for guile-devel@gnu.org; Sun, 29 Jan 2006 13:48:08 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1F3Ham-0003cY-Tk for guile-devel@gnu.org; Sun, 29 Jan 2006 13:48:05 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F3Ham-0003cU-RR for guile-devel@gnu.org; Sun, 29 Jan 2006 13:48:04 -0500 Original-Received: from [213.243.153.37] (helo=smtp1.pp.htv.fi) by monty-python.gnu.org with esmtp (Exim 4.52) id 1F3HYx-0000Gl-GD for guile-devel@gnu.org; Sun, 29 Jan 2006 13:46:11 -0500 Original-Received: from zagadka.ping.de (cs181072157.pp.htv.fi [82.181.72.157]) by smtp1.pp.htv.fi (Postfix) with SMTP id 754FE7FCDB for ; Sun, 29 Jan 2006 20:44:58 +0200 (EET) Original-Received: (qmail 1487 invoked by uid 1000); 29 Jan 2006 20:44:52 +0200 Original-To: djurfeldt@nada.kth.se In-Reply-To: <66e540fe0512220156s47532d1co5841d7eef2e898de@mail.gmail.com> (Mikael Djurfeldt's message of "Thu, 22 Dec 2005 10:56:20 +0100") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.devel:5639 Archived-At: Mikael Djurfeldt writes: > For now, I will not work further on that code. To the Guile > developers I suggest that you do what you want. Fix it, or back out > the future feature entirely. Hmm. Semantically, 'begin-thread' and 'thread-join' should be (nearly?) identical to 'future' and 'future-ref', so we are not losing critical functionality when removing futures. However, it would still be good to have some kind of thread pool for the case where you want to use many short lived threads. So, I'll remove futures from the API, but leave the code there. -- GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405 _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://lists.gnu.org/mailman/listinfo/guile-devel