From: Tom Gillespie <tgbugs@gmail.com>
To: Taylan Kammer <taylan.kammer@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: reading symbols containing apostrophe
Date: Mon, 4 Jan 2021 18:12:27 -0500 [thread overview]
Message-ID: <CA+G3_POcgqzwr9dAJcETWTgNPvLmS6jZQwM75icKgHYKSSR4hQ@mail.gmail.com> (raw)
In-Reply-To: <317b8cc8-659a-bfe0-e8c1-26df8c0f0fd5@gmail.com>
Hi Taylan,
Thank you for the explanation. Replies in line. Best!
Tom
> It's quite common for implementations to extend the standard, so
> something that's "an error" in the standard might be allowed in an
> implementation.
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).
> This is evidently one of those cases.
Unfortunate that it does not seem to be documented anywhere.
Would it make sense to bring this up on the dev mailing list and
submit a patch to the documentation to indicate where guile is
incompatible with the standard?
> I would not *rely* on Guile supporting this either though. Maybe in a
> future version the reader will be changed and it will stop working.
For now I will mark it as a quirk that will have to be tracked.
next prev parent reply other threads:[~2021-01-04 23:12 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 [this message]
2021-01-05 13:23 ` Taylan Kammer
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=CA+G3_POcgqzwr9dAJcETWTgNPvLmS6jZQwM75icKgHYKSSR4hQ@mail.gmail.com \
--to=tgbugs@gmail.com \
--cc=guile-user@gnu.org \
--cc=taylan.kammer@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).