From: Maxime Devos <maximedevos@telenet.be>
To: Chris Vine <vine24683579@gmail.com>, guile-user@gnu.org
Subject: Re: Question about an error with ports
Date: Fri, 11 Mar 2022 20:48:27 +0100 [thread overview]
Message-ID: <0bb10bc0517975226fbc42bdc36147def27c90b0.camel@telenet.be> (raw)
In-Reply-To: <20220311181317.eddaee41c7293abb432c8321@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 495 bytes --]
Chris Vine schreef op vr 11-03-2022 om 18:13 [+0000]:
> Interestingly the read procedure remains unsafe in guile-2.2.6, but
> seems to be safe in guile-3.0.8 even though I cannot see what in the
This is probably due to the rewrite of the 'read' procedure in Scheme
(see module/ice-9/read.scm (cannot be imported as a module)). There's
still a C version of the read procedure, but as I understand it it is
only for bootstrapping (and maybe performance, I dunno).
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-03-11 19:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 1:26 Question about an error with ports Zelphir Kaltstahl
2022-03-10 15:05 ` Olivier Dion via General Guile related discussions
2022-03-10 22:32 ` Zelphir Kaltstahl
2022-03-10 23:46 ` Olivier Dion via General Guile related discussions
2022-03-11 12:05 ` Chris Vine
2022-03-11 14:58 ` Olivier Dion via General Guile related discussions
2022-03-11 17:26 ` Chris Vine
2022-03-11 17:47 ` Olivier Dion via General Guile related discussions
2022-03-11 18:13 ` Chris Vine
2022-03-11 19:48 ` Maxime Devos [this message]
2022-03-11 19:49 ` Maxime Devos
2022-03-12 0:10 ` Chris Vine
2022-03-12 0:27 ` Chris Vine
2022-03-11 12:11 ` Maxime Devos
2022-03-11 15:06 ` Olivier Dion via General Guile related discussions
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=0bb10bc0517975226fbc42bdc36147def27c90b0.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=guile-user@gnu.org \
--cc=vine24683579@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).