From: "Ludovic Courtès" <ludo@gnu.org>
To: Dmitry Alexandrov <dag@gnui.org>
Cc: guile-devel@gnu.org
Subject: Re: (. wtf?)
Date: Wed, 10 May 2023 18:25:00 +0200 [thread overview]
Message-ID: <87h6sk8883.fsf@gnu.org> (raw)
In-Reply-To: <5y949ftu.dag@gnui.org> (Dmitry Alexandrov's message of "Sun, 07 May 2023 21:06:21 +0300")
HI,
Dmitry Alexandrov <dag@gnui.org> skribis:
> On Fri, 05 May 2023 16:35 Ludovic Courtès <civodul@toot.aquilenet.fr> wrote:
>> (call-with-input-string "(. wtf?)" read)
>>
>> ⇒ wtf?
>>
>> #Guile #Scheme
>
> Hey!^W Sorry...
>
> Dear Guile developer,
>
> your tweet made me deeply concerned. Is it a sign that this behaviour is going to be ‘fixed’ eventually?
I should clarify that it’s definitely a weird corner case, but not
something I’m worried about.
As I mentioned on Mastodon, Guile’s ‘read’ has always worked like that I
suppose; when he rewrite ‘read’ in Scheme, Andy took care to preserve
the exact same behavior, even for weird cases like this one.
We could remove support for it as it doesn’t bring anything, but I don’t
see any pressure to do so.
Ludo’.
prev parent reply other threads:[~2023-05-10 16:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <110317045333325207.civodul@toot.aquilenet.fr>
2023-05-07 18:06 ` (. wtf?) Dmitry Alexandrov
2023-05-07 19:44 ` Dr. Arne Babenhauserheide
2023-05-08 4:32 ` tomas
2023-05-08 5:31 ` Dr. Arne Babenhauserheide
2023-05-08 6:50 ` tomas
2023-05-08 10:45 ` Dmitry Alexandrov
2023-05-08 10:53 ` Dmitry Alexandrov
2023-05-08 10:58 ` tomas
2023-05-10 16:25 ` Ludovic Courtès [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=87h6sk8883.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dag@gnui.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).