From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Thien-Thi Nguyen Newsgroups: gmane.emacs.devel Subject: Re: ELisp futures and continuations/coroutines Date: Thu, 19 May 2011 18:40:47 +0200 Message-ID: <87hb8qwsmo.fsf@ambire.localdomain> References: <87fwogaxzb.fsf@stupidchicken.com> <87mxilezg8.fsf@lifelogs.com> <87boz0eov8.fsf@lifelogs.com> <87mxikrulm.fsf@lifelogs.com> <871uzw5asv.fsf@lifelogs.com> <878vu2ztua.fsf_-_@lifelogs.com> <87oc2ywwuy.fsf@ambire.localdomain> <87r57uyaeu.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1305823342 22905 80.91.229.12 (19 May 2011 16:42:22 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 19 May 2011 16:42:22 +0000 (UTC) Cc: emacs-devel@gnu.org To: Ted Zlatanov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu May 19 18:42:14 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QN6IZ-0005hv-3i for ged-emacs-devel@m.gmane.org; Thu, 19 May 2011 18:42:07 +0200 Original-Received: from localhost ([::1]:45241 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QN6IY-00007f-GS for ged-emacs-devel@m.gmane.org; Thu, 19 May 2011 12:42:06 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:58035) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QN6IV-00007O-LL for emacs-devel@gnu.org; Thu, 19 May 2011 12:42:04 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QN6IU-0008Lc-FH for emacs-devel@gnu.org; Thu, 19 May 2011 12:42:03 -0400 Original-Received: from smtp208.alice.it ([82.57.200.104]:48547) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QN6IU-0008LQ-6M for emacs-devel@gnu.org; Thu, 19 May 2011 12:42:02 -0400 Original-Received: from ambire.localdomain (87.5.65.6) by smtp208.alice.it (8.5.124.08) id 4C1A27161A316F96; Thu, 19 May 2011 18:41:59 +0200 Original-Received: from ttn by ambire.localdomain with local (Exim 4.69) (envelope-from ) id 1QN6HH-00026Q-L9; Thu, 19 May 2011 18:40:47 +0200 In-Reply-To: <87r57uyaeu.fsf@lifelogs.com> (Ted Zlatanov's message of "Thu, 19 May 2011 10:31:21 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 82.57.200.104 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:139524 Archived-At: () Ted Zlatanov () Thu, 19 May 2011 10:31:21 -0500 You mean fsm-0.1ttn5.el from gnu.emacs.sources? (http://lists.gnu.org/archive/html/gnu-emacs-sources/2007-02/msg00006.ht= ml) Yes, or the original (also to gnu-emacs-sources). Same idea. Do you want to provide an example of how it would work to tie a hypothetical future type with process sentinels through fsm.el? It seems reasonable but I don't know enough to say. No, because i don't know what such a future type would do. I just know that i have successfully (and more pleasantly than initially imagined) used fsm to implement a multicast proxy server (1 in, N out), which had as its core requirement, the ability to chunk computation into disparate pieces to be evaluated later. From this congruent experience, i would guess that a "future type" would be some subset of the fsm internals. Analogous to the "keymap type", which is really just a list with symbol =E2=80=98keymap=E2=80=99 in its CAR, i am guessing one could poke around fs= m internals and derive a "future type", without having to go to C. Which is to say, i also don't know enough to say, but i see a similarity. --=20 a sig, not big, i fig, you dig?