From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Subject: Re: srfi-88 keyword / symbol ambiguity
Date: Mon, 21 Jul 2008 12:04:05 +0200 [thread overview]
Message-ID: <87r69neep6.fsf@gnu.org> (raw)
In-Reply-To: 2bc5f8210807201335v3f2ceaf0lb250c35b54ff4727@mail.gmail.com
Hi,
"Julian Graham" <joolean@gmail.com> writes:
> guile> (keyword? 'foo:)
> #t
This is expected, per SRFI-88.
> 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)'.
Good point. Alas, that's hardly avoidable, given that the above
behavior is defined by SRFI-88.
One way to avoid it would be to not have a mutable global reader. This
can be achieved using the `current-reader' fluid and something like
Guile-Reader, which produces immutable `read' procedures:
http://www.nongnu.org/guile-reader/doc/guile-reader.html#Quick-Start
Thanks,
Ludovic.
next prev parent reply other threads:[~2008-07-21 10:04 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 [this message]
2008-07-21 12:18 ` Neil Jerram
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=87r69neep6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-user@gnu.org \
/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).