Re: `set!' of generated temporary in macro expansion causes warning

[Andreas Rottmann]

Stefan Israelsson Tampe <address@hidden> writes:

> One thing that can go wrong is that we generate a lot of gensymed variables
> in current-module
>
> So be careful and have a peek at the defined module variables to see if
> doesn't get polluted
>
The use of `generate-temporaries' is actually a workaround for Guile
currently breaking hygiene when a macro introduces a top-level
identifier.  Anyway, the namespace certainly will get polluted, but
there's no way around it with current Guile -- see also
<https://savannah.gnu.org/bugs/?31472>, and
<http://lists.gnu.org/archive/html/guile-devel/2011-02/msg00241.html>.

I think (but can't find the message ATM) that Andy has changed his mind
from what he stated in his immediate reply to the bug report, and is now
in favor of eventually making macro-introduced names hygienic; but IIRC
there has not yet been found a way to avoid namespace pollution.

Regards, Rotty

PS: Would you consider avoiding top-posting, and doing a "full reply" in
    your MUA, so the mailing list (address@hidden) gets a copy of
    your messagess as well?