From: "Julian Graham" <joolean@gmail.com>
To: "Guile User" <guile-user@gnu.org>
Subject: srfi-88 keyword / symbol ambiguity
Date: Sun, 20 Jul 2008 16:35:43 -0400 [thread overview]
Message-ID: <2bc5f8210807201335v3f2ceaf0lb250c35b54ff4727@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1272 bytes --]
Hi,
It looks like the changes to the reader to support SRFI-88-style keywords
lead to some ambiguities when it comes to whether a token is a symbol or a
keyword. Specifically, it's no longer possible to create a symbol via
quoting if that symbol ends in a colon:
guile> (use-modules (srfi srfi-88))
guile> (keyword? foo:)
#t
guile> (keyword? 'foo:)
#t
guile> (symbol->string 'foo:)
Backtrace:
In standard input:
6: 0* [symbol->string {#:foo}]
standard input:6:1: In procedure symbol->string in expression
(symbol->string (begin #)):
standard input:6:1: Wrong type argument in position 1 (expecting symbol):
#:foo
ABORT: (wrong-type-arg)
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)'.
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.
Regards,
Julian
[-- Attachment #2: Type: text/html, Size: 1467 bytes --]
next reply other threads:[~2008-07-20 20:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-20 20:35 Julian Graham [this message]
2008-07-21 10:04 ` srfi-88 keyword / symbol ambiguity Ludovic Courtès
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=2bc5f8210807201335v3f2ceaf0lb250c35b54ff4727@mail.gmail.com \
--to=joolean@gmail.com \
--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).