From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tom Tromey Newsgroups: gmane.emacs.devel Subject: Re: the state of the concurrency branch Date: Mon, 21 Oct 2013 09:08:04 -0600 Message-ID: <87mwm2ll0r.fsf@fleche.redhat.com> 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 1382368100 22960 80.91.229.3 (21 Oct 2013 15:08:20 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2013 15:08:20 +0000 (UTC) Cc: Barry OReilly , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Oct 21 17:08:23 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 1VYH5j-000103-12 for ged-emacs-devel@m.gmane.org; Mon, 21 Oct 2013 17:08:23 +0200 Original-Received: from localhost ([::1]:40374 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VYH5i-0006uY-GA for ged-emacs-devel@m.gmane.org; Mon, 21 Oct 2013 11:08:22 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47965) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VYH5b-0006uC-P6 for emacs-devel@gnu.org; Mon, 21 Oct 2013 11:08:20 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VYH5X-0001H4-0f for emacs-devel@gnu.org; Mon, 21 Oct 2013 11:08:15 -0400 Original-Received: from mx1.redhat.com ([209.132.183.28]:53321) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VYH5W-0001Gt-PS for emacs-devel@gnu.org; Mon, 21 Oct 2013 11:08:10 -0400 Original-Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r9LF86Mr028831 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 21 Oct 2013 11:08:06 -0400 Original-Received: from barimba (ovpn-113-54.phx2.redhat.com [10.3.113.54]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r9LF848N022798 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 21 Oct 2013 11:08:05 -0400 X-Attribution: Tom In-Reply-To: (Stefan Monnier's message of "Sat, 19 Oct 2013 17:42:41 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) X-Scanned-By: MIMEDefang 2.68 on 10.5.11.25 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 209.132.183.28 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:164418 Archived-At: >>>>> "Stefan" == Stefan Monnier writes: >> 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. Stefan> In theory you could imagine a scheme where timers inherit the dynamic Stefan> bindings that are in place when the timer is setup (or when the process Stefan> is started). Stefan> It wouldn't provide the exact same behavior we have currently, butit Stefan> might be made close enough to give the right behavior in practice in Stefan> most cases. I had actually implemented this for new threads, but you had me take it out again :) I think this would be too magical to do just for timers. For one thing, 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. So the scheme would have to be more complicated. Tom