Re: byte-compile-file not reentrant?

[Lennart Borgman <lennart.borgman@gmail.com>]

On Wed, Dec 30, 2009 at 4:17 AM, Daniel Colascione
<daniel@censorshipresearch.org> wrote:
> -----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.


Hm, thanks. Then I have to change strategy.

I do not understand what is happening. I got trouble with defmacro:s
that are in some way half defined sometimes. I am rewriting require to
download from the web (as I (implicitly) told in another message). But
this creates of course some problem with loading. But the expansion of
defmacro is a black hole for me.

Can I just use catch+throw to jump out of a compilation when I detect
a require (and reque compilation)? Or are there some state to cleanup?