From: Pascal Bourguignon <spam@thalassa.informatimago.com>
Subject: Re: Lisp help: problem with uninterned symbols
Date: 12 Dec 2003 18:17:13 +0100 [thread overview]
Message-ID: <87fzfqot0m.fsf@thalassa.informatimago.com> (raw)
In-Reply-To: mailman.1639.1071247380.399.help-gnu-emacs@gnu.org
Lars Brinkhoff <lars@nocrew.org> writes:
> Pascal Bourguignon <spam@thalassa.informatimago.com> writes:
> > Doctor, when I do this, it hurts!
>
> I still need to do it, and I'm willing to endure some pain.
>
> > You have the solution: encapsulate your compilation units in a progn.
>
> Not quite. As I wrote:
>
> > > that trick doesn't work if foo and bar are defined in two separate
> > > file[s].
It seems to me that it's a "feature" of the byte compiler. It just
does not search an uninterned symbols amongst all uninterned symbols
ever created to find if there's another occurence.
One question: why don't you use an obarray for you symbols?
(I doubt that would change anything thought).
What about interning all your symbols as normal emacs lisp symbols.
Of course, you may want to prefix their names with a "package" name.
Otherwise, I'm afraid you'll have to extend the emacs byte compiler to
allow it to work with various sources of "interned" symbols.
--
__Pascal_Bourguignon__ . * * . * .* .
http://www.informatimago.com/ . * . .*
There is no worse tyranny than to force * . . /\ () . *
a man to pay for what he does not . . / .\ . * .
want merely because you think it .*. / * \ . .
would be good for him. -- Robert Heinlein . /* o \ .
http://www.theadvocates.org/ * '''||''' .
SCO Spam-magnet: postmaster@sco.com ******************
next prev parent reply other threads:[~2003-12-12 17:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1638.1071244137.399.help-gnu-emacs@gnu.org>
2003-12-12 15:09 ` Lisp help: problem with uninterned symbols Pascal Bourguignon
2003-12-12 15:40 ` Lars Brinkhoff
[not found] ` <mailman.1639.1071247380.399.help-gnu-emacs@gnu.org>
2003-12-12 17:17 ` Pascal Bourguignon [this message]
2003-12-12 21:59 ` Lars Brinkhoff
2003-12-12 23:37 ` Lars Brinkhoff
2003-12-12 19:54 ` Stefan Monnier
2003-12-12 20:44 ` Lars Brinkhoff
2003-12-12 14:46 Lars Brinkhoff
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fzfqot0m.fsf@thalassa.informatimago.com \
--to=spam@thalassa.informatimago.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).