Re: Why can't `gnus-draft-setup' be bytecompiled?

[Hallvard B Furuseth <h.b.furuseth@usit.uio.no>]

Hrvoje Niksic <hniksic@srce.hr> writes:

> You will note that `gnus-setup-message' makes use of uninterned
> symbols to make macro execution safe.  While this method works in the
> interpreter, it fails for compile code because the reader interns the
> symbols in the obarray.

In practice, this means that the byte-compiled version reserves these
variable names (so they may not be used outside this macr), and uses
them directly without make-symbol.  That should be OK unless the macro
can give these variables as arguments to another instance of itself.

> This has been fixed by introducing the `#:' gensym syntax and making
> the byte-compiler emit it by default.  FSFmacs 20 contains the same
> fix, courtesy Erik Naggum.

A hack which works in emacs19 as well is to replace (make-symbol "foo")
with (gensym "foo").  It appends a unique-per-session number to "foo"
and then does make-symbol.

-- 
Hallvard