From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: the state of the concurrency branch Date: Mon, 21 Oct 2013 14:17:39 -0400 Message-ID: References: <871u3js17r.fsf@fleche.redhat.com> <87r4biphpg.fsf@fleche.redhat.com> <87mwm2ll0r.fsf@fleche.redhat.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1382379480 6642 80.91.229.3 (21 Oct 2013 18:18:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2013 18:18:00 +0000 (UTC) Cc: Tom Tromey , emacs-devel@gnu.org To: Barry OReilly Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Oct 21 20:18:03 2013 Return-path: Envelope-to: ged-emacs-devel@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 1VYK3F-0003Yp-2Z for ged-emacs-devel@m.gmane.org; Mon, 21 Oct 2013 20:18:01 +0200 Original-Received: from localhost ([::1]:41116 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VYK3E-0005iC-JG for ged-emacs-devel@m.gmane.org; Mon, 21 Oct 2013 14:18:00 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37347) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VYK33-0005Yz-Bm for emacs-devel@gnu.org; Mon, 21 Oct 2013 14:17:56 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VYK2v-00062a-Th for emacs-devel@gnu.org; Mon, 21 Oct 2013 14:17:49 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]:53193) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VYK2v-000628-PW for emacs-devel@gnu.org; Mon, 21 Oct 2013 14:17:41 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4EABK/CFFFxLCX/2dsb2JhbABEvw4Xc4IeAQEEAVYjEAs0EhQYDSSIHgbBLZEKA6R6gV6DEw X-IPAS-Result: Av4EABK/CFFFxLCX/2dsb2JhbABEvw4Xc4IeAQEEAVYjEAs0EhQYDSSIHgbBLZEKA6R6gV6DEw X-IronPort-AV: E=Sophos;i="4.84,565,1355115600"; d="scan'208";a="35999063" Original-Received: from 69-196-176-151.dsl.teksavvy.com (HELO pastel.home) ([69.196.176.151]) by ironport2-out.teksavvy.com with ESMTP/TLS/ADH-AES256-SHA; 21 Oct 2013 14:17:40 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 91DB760026; Mon, 21 Oct 2013 14:17:39 -0400 (EDT) In-Reply-To: (Barry OReilly's message of "Mon, 21 Oct 2013 12:07:37 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.182 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:164430 Archived-At: >> I think a typical reason to do this kind of funny business is to >> communicate from the timer (or process filter or whatever) back to >> the caller. > For this use case, wouldn't a feature for thread futures be appropriate? For process filters/sentinels, you can almost always replace the dynamically scoped variable with a process property. We could add timer properties for that same purpose. Tho, there are already many other ways to get the same result without relying on dynamic bindings. Stefan