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: Sat, 19 Oct 2013 17:42:41 -0400 Message-ID: References: <871u3js17r.fsf@fleche.redhat.com> <87r4biphpg.fsf@fleche.redhat.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1382218980 1509 80.91.229.3 (19 Oct 2013 21:43:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 19 Oct 2013 21:43: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 Sat Oct 19 23:43:01 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 1VXeIX-0000HK-A8 for ged-emacs-devel@m.gmane.org; Sat, 19 Oct 2013 23:43:01 +0200 Original-Received: from localhost ([::1]:34484 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VXeIW-0002my-LL for ged-emacs-devel@m.gmane.org; Sat, 19 Oct 2013 17:43:00 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59637) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VXeIM-0002ml-8T for emacs-devel@gnu.org; Sat, 19 Oct 2013 17:42:57 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VXeIE-0000iG-VP for emacs-devel@gnu.org; Sat, 19 Oct 2013 17:42:50 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]:33795) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VXeIE-0000iC-RQ for emacs-devel@gnu.org; Sat, 19 Oct 2013 17:42:42 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4EABK/CFFsr+kq/2dsb2JhbABEvw4Xc4IeAQEEAVYjBQsLNBIUGA0kiB4GwS2RCgOkeoFegxM X-IPAS-Result: Av4EABK/CFFsr+kq/2dsb2JhbABEvw4Xc4IeAQEEAVYjBQsLNBIUGA0kiB4GwS2RCgOkeoFegxM X-IronPort-AV: E=Sophos;i="4.84,565,1355115600"; d="scan'208";a="35890043" Original-Received: from 108-175-233-42.dsl.teksavvy.com (HELO pastel.home) ([108.175.233.42]) by ironport2-out.teksavvy.com with ESMTP/TLS/ADH-AES256-SHA; 19 Oct 2013 17:42:42 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 04FD9608B1; Sat, 19 Oct 2013 17:42:41 -0400 (EDT) In-Reply-To: (Barry OReilly's message of "Sat, 19 Oct 2013 15:29:38 -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:164382 Archived-At: > Theoretically, it's already true on trunk that timers can run with > different dynamic bindings each time it runs. sit-for is called from > various places, timers can run within timers, and all can dynamically > bind variables. In theory you could imagine a scheme where timers inherit the dynamic bindings that are in place when the timer is setup (or when the process is started). It wouldn't provide the exact same behavior we have currently, butit might be made close enough to give the right behavior in practice in most cases. Stefan