From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Daniel Colascione Newsgroups: gmane.emacs.devel Subject: Re: byte-compile-file not reentrant? Date: Tue, 29 Dec 2009 22:17:51 -0500 Organization: Censorship Research Center Message-ID: <4B3AC65F.6020105@censorshipresearch.org> References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1262143098 19470 80.91.229.12 (30 Dec 2009 03:18:18 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 30 Dec 2009 03:18:18 +0000 (UTC) Cc: Emacs-Devel devel To: Lennart Borgman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Dec 30 04:18:10 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1NPp4Z-00063x-KN for ged-emacs-devel@m.gmane.org; Wed, 30 Dec 2009 04:18:08 +0100 Original-Received: from localhost ([127.0.0.1]:37160 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NPp4Z-0005ma-QL for ged-emacs-devel@m.gmane.org; Tue, 29 Dec 2009 22:18:07 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NPp4V-0005mL-Ta for emacs-devel@gnu.org; Tue, 29 Dec 2009 22:18:03 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NPp4U-0005kh-Af for emacs-devel@gnu.org; Tue, 29 Dec 2009 22:18:03 -0500 Original-Received: from [199.232.76.173] (port=59035 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NPp4U-0005kV-3d for emacs-devel@gnu.org; Tue, 29 Dec 2009 22:18:02 -0500 Original-Received: from haystack.austinheap.com ([70.32.98.68]:55706 helo=haystacknetwork.com) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NPp4T-0006vg-Ul for emacs-devel@gnu.org; Tue, 29 Dec 2009 22:18:02 -0500 User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 In-Reply-To: X-Enigmail-Version: 1.0 X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:119004 Archived-At: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/29/09 9:58 PM, Lennart Borgman wrote: > A buffer created with (get-buffer-create " *Compiler Input*") makes > byte-compile-file not reentrant if I understand it correctly. (I did > not look very carefully.) > > I do not understand the meaning of this. Should the old buffer be > reused in some way? > > There is a similar call in byte-compile-from-buffer. > > Could perhaps these calls be changed to generate new buffer names? > Would that make byte compiling reentrant or are there other > restrictions that makes this impossible? I looked into this a bit when I wrote byte-code-cache.el. The buffer name is just the first obstacle to a re-entrant byte compiler: there are various variable bindings that would be hard to catch and sort out. TBH, it'd probably be easier to just re-execute emacs itself, in batch mode, as a subprocess. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (Darwin) iEYEARECAAYFAks6xl8ACgkQ17c2LVA10VuwBQCgn7Jwf0xL/PjKOPmM+T7ffdYu JV4AoLEaSRnOKSIb7c4kilEEuP4AvxJ6 =EIDE -----END PGP SIGNATURE-----