From: Taylan Kammer <taylan.kammer@gmail.com>
To: Tom Gillespie <tgbugs@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: reading symbols containing apostrophe
Date: Tue, 5 Jan 2021 14:23:32 +0100 [thread overview]
Message-ID: <0d469566-434a-6d30-67b1-846e6c2f9777@gmail.com> (raw)
In-Reply-To: <CA+G3_POcgqzwr9dAJcETWTgNPvLmS6jZQwM75icKgHYKSSR4hQ@mail.gmail.com>
On 05.01.2021 00:12, Tom Gillespie wrote:
> In this instance I think the situation is worse than if the standard
> said this was an error. In fact the standard doesn't say this is an
> error at all, which would be better than the current situation.
> Where nearly all other implementations will read 'a'b'c as three
> separate symbols, Guile reads it as a single symbol, silently
> diverging from the standard without warning (until something
> comes crashing down as a result of the difference later).
Hmm, I'm looking at the R7RS-small BNF (haven't checked the other
standards) and I think you're right.
The apostrophe is a token of its own, along with <identifier>, which I
think would mean that 'foo'bar should be parsed as four tokens.
It might be worth taking this up with the devel mailing list then.
- Taylan
prev parent reply other threads:[~2021-01-05 13:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 4:51 reading symbols containing apostrophe Tom Gillespie
2020-12-30 13:02 ` Taylan Kammer
2021-01-04 23:12 ` Tom Gillespie
2021-01-05 13:23 ` Taylan Kammer [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=0d469566-434a-6d30-67b1-846e6c2f9777@gmail.com \
--to=taylan.kammer@gmail.com \
--cc=guile-user@gnu.org \
--cc=tgbugs@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).