From: ludo@gnu.org (Ludovic Courtès)
To: 30066@debbugs.gnu.org
Cc: Andy Wingo <wingo@igalia.com>
Subject: bug#30066: 'get-bytevector-some' returns only 1 byte from unbuffered ports
Date: Wed, 10 Jan 2018 16:02:10 +0100 [thread overview]
Message-ID: <87zi5lrc3x.fsf@gnu.org> (raw)
As discussed on IRC, ‘get-bytevector-some’ returns only 1 byte from
unbuffered ports:
--8<---------------cut here---------------start------------->8---
scheme@(guile-user)> (call-with-input-string "foo"
(lambda (port)
(setvbuf port _IONBF)
(get-bytevector-some port)))
$11 = #vu8(102)
scheme@(guile-user)> (version)
$12 = "2.2.3"
--8<---------------cut here---------------end--------------->8---
Strictly speaking it’s valid, but in practice it’s not very useful.
AFAICS, we lack a way to do the equivalent of:
read (fd, buf, sizeof buf);
‘get-bytevector-n!’ is different because it blocks until it has read
COUNT bytes or EOF is reached. So ‘get-bytevector-some’ could play this
role, but it doesn’t.
Thoughts?
Ludo’.
next reply other threads:[~2018-01-10 15:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 15:02 Ludovic Courtès [this message]
2018-01-10 15:59 ` bug#30066: 'get-bytevector-some' returns only 1 byte from unbuffered ports Ludovic Courtès
2018-01-10 16:32 ` Andy Wingo
2018-01-10 16:58 ` Nala Ginrut
2018-01-10 17:26 ` Andy Wingo
2018-01-10 17:43 ` Nala Ginrut
2018-01-11 14:34 ` Ludovic Courtès
2018-01-11 19:55 ` Mark H Weaver
2018-01-11 21:02 ` Ludovic Courtès
2018-01-11 21:55 ` Mark H Weaver
2018-01-12 9:01 ` Andy Wingo
2018-01-12 10:15 ` Ludovic Courtès
2018-01-12 10:33 ` Andy Wingo
2018-01-13 20:53 ` Ludovic Courtès
2018-02-16 13:19 ` Ludovic Courtès
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=87zi5lrc3x.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30066@debbugs.gnu.org \
--cc=wingo@igalia.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).