From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: Why can't `gnus-draft-setup' be bytecompiled?
Date: 10 Mar 1998 00:19:27 +0100 [thread overview]
Message-ID: <kigwwe3xxj4.fsf@jagor.srce.hr> (raw)
In-Reply-To: SL Baur's message of "09 Mar 1998 15:01:57 -0800"
SL Baur <steve@xemacs.org> writes:
> `gnus-draft-setup' is wrapped in a progn and has the annotation:
>
> ;;;!!!If this is byte-compiled, it fails miserably.
> ;;;!!!I have no idea why.
>
> I just tried it bytecompiled and it seemed to work. What was/is
> broken about it? If it's an editor bug I want to fix it.
It is probably a manifestation of the bug I've fixed a few betas ago.
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.
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.
--
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
A radioactive cat has eighteen half-lives.
next prev parent reply other threads:[~1998-03-09 23:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-09 23:01 SL Baur
1998-03-09 23:19 ` Hrvoje Niksic [this message]
1998-03-13 21:39 ` Lars Magne Ingebrigtsen
1998-03-14 3:11 ` Hallvard B Furuseth
1998-03-14 3:23 ` Hrvoje Niksic
1998-03-14 4:09 ` Aaron M. Ucko
1998-03-19 12:30 ` Lars Magne Ingebrigtsen
1998-03-21 2:09 ` Aaron M. Ucko
1998-03-23 13:15 ` Lars Magne Ingebrigtsen
1998-03-14 2:29 ` Hallvard B Furuseth
1998-03-19 12:25 ` Lars Magne Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=kigwwe3xxj4.fsf@jagor.srce.hr \
--to=hniksic@srce.hr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).