From: Chris Vine <vine24683579@gmail.com>
To: guile-user@gnu.org
Subject: Re: Question about an error with ports
Date: Fri, 11 Mar 2022 18:13:17 +0000 [thread overview]
Message-ID: <20220311181317.eddaee41c7293abb432c8321@gmail.com> (raw)
In-Reply-To: <20220311172650.aeab7bf504b38992196e0141@gmail.com>
On Fri, 11 Mar 2022 17:26:50 +0000
Chris Vine <vine24683579@gmail.com> wrote:
> Notable procedures which it appears remain as non-suspendable are
> get-bytevector-all, get-string-n, read, write and display, but to be
> sure about the first two of those I would also need to read the source
> again. A few years ago I had some test code to test which procedures
> were suspendable and I will also have to see if I can find it again.
I have resurrected my old test code and I can confirm that
get-bytevector-n, get-bytevector-n!, get-bytevector-some and
get-bytevector-some! are now suspension safe in guile-2.2.6 and
guile-3.0.8, but get-bytevector-all, get-string-n and get-string-n!
remain unsafe.
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
code has changed. I have yet to re-equip my tests to test the write and
display procedures, or to see what effect this has on http-get,
http-put and the like.
Chris
next prev parent reply other threads:[~2022-03-11 18:13 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 [this message]
2022-03-11 19:48 ` Maxime Devos
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=20220311181317.eddaee41c7293abb432c8321@gmail.com \
--to=vine24683579@gmail.com \
--cc=guile-user@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).