From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Syntax for symbols is more permissive than R6RS
Date: Fri, 24 Apr 2009 17:27:51 +0200 [thread overview]
Message-ID: <874owexea0.fsf@gnu.org> (raw)
In-Reply-To: 1240558064.3133.147.camel@localhost.localdomain
Hi!
Mike Gran <spk121@yahoo.com> writes:
> I was poking around the reader while working on the Unicode stuff, and I
> found that there aren't checks for a lot of symbol names that R6RS
> considers to be invalid.
It's actually more permissive than R5RS as well. For instance, `1+' and
`1-' are not valid R5RS identifiers IIRC.
I would be inclined to not change the reader's default behavior, i.e.,
to remain at least as permissive as in 1.8, so as to not cause
gratuitous incompatibility (we could even add unit tests to make sure we
don't remove them inadvertently.)
However, it may be a good idea to have a reader option asking for
strict(er) conformance.
Thanks,
Ludo'.
next prev parent reply other threads:[~2009-04-24 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 7:27 Syntax for symbols is more permissive than R6RS Mike Gran
2009-04-24 15:27 ` Ludovic Courtès [this message]
2009-04-27 20:26 ` 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=874owexea0.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@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).