Re: byte-compile-file not reentrant?

[Daniel Colascione]

-----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-----