From: "Neil Jerram" <neiljerram@googlemail.com>
To: "Julian Graham" <joolean@gmail.com>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: srfi-88 keyword / symbol ambiguity
Date: Mon, 21 Jul 2008 13:18:25 +0100 [thread overview]
Message-ID: <49dd78620807210518j64fdf7e4m6b3e935ffd9763c9@mail.gmail.com> (raw)
In-Reply-To: <2bc5f8210807201335v3f2ceaf0lb250c35b54ff4727@mail.gmail.com>
2008/7/20 Julian Graham <joolean@gmail.com>:
>
> This is particularly bad because it breaks a lot of code that calls
> `use-modules' with the :prefix or :rename syntax -- from looking at some of
> the core libraries, it seems like it's pretty common to use rename-prefixes
> that end in a colon. So, for example, the ice-9 debugger modules don't work
> after loading `(srfi srfi-88)'.
If it helps you in the short term, please feel free to look at
patching those modules so that they use a prefix that doesn't end with
a colon. I think that should be compatible in API terms, because the
prefixed names are only used internally within the using module.
> I'm not sure yet what the fix would be -- maybe the reader should avoid
> converting a token into a postfix-style keyword if it's obvious from the
> read state that a symbol is desired (i.e., the quote character is prefixed),
> but that probably doesn't cover all the possibilities.
That sounds very tricky! As Ludovic said, I think read options need
somehow to be less global - whether via Guile-Reader, or otherwise.
Neil
prev parent reply other threads:[~2008-07-21 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-20 20:35 srfi-88 keyword / symbol ambiguity Julian Graham
2008-07-21 10:04 ` Ludovic Courtès
2008-07-21 12:18 ` Neil Jerram [this message]
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49dd78620807210518j64fdf7e4m6b3e935ffd9763c9@mail.gmail.com \
--to=neiljerram@googlemail.com \
--cc=guile-user@gnu.org \
--cc=joolean@gmail.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).