From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Subject: Re: Nonblocking get-bytevector-n bug?
Date: Mon, 07 Dec 2015 10:50:51 +0100 [thread overview]
Message-ID: <87poyilh8k.fsf@gnu.org> (raw)
In-Reply-To: 87h9jvuxb3.fsf@elektro.pacujo.net
Marko Rauhamaa <marko@pacujo.net> skribis:
> Of these, only get-bytevector-some seems to behave as expected when the
> port is nonblocking:
>
> ========================================================================
> (use-modules (rnrs io ports)
> (rnrs bytevectors))
>
> (let ((port (fdes->inport 0)))
> (fcntl port F_SETFL (logior O_NONBLOCK (fcntl port F_GETFL)))
> (let loop ()
> (catch 'system-error
> (lambda ()
> (format #t "~s\n" (get-bytevector-some port)))
> (lambda syserr
> (format #t "err ~s\n" (system-error-errno syserr))))
> (sleep 1)
> (loop)))
> ========================================================================
>
> If you replace (get-bytevector-some port) with
> (get-bytevector-n port 8192) or (get-bytevector-n! port bv 0 8192),
> no partial data is returned.
That’s because get-bytevector-n{,!} are specified as blocking if
necessary until N bytes are read or EOF is reached.
> The problem with get-bytevector-some is that there is no limit to how
> many bytes might be returned. In practice, I see that the amount is
> capped at 4096 bytes, but the documentation does not guarantee any
> limit.
Right, the R6RS specification of that procedure doesn’t tell anything
more either.
It was criticized back in the day partly for that reason:
http://www.r6rs.org/formal-comments/comment-224.txt
I think a ‘get-bytevector-some!’ procedure could address the issue.
Not sure what R7 does here.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2015-12-07 9:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-06 20:38 Nonblocking get-bytevector-n bug? Marko Rauhamaa
2015-12-07 9:50 ` Ludovic Courtès [this message]
2015-12-07 10:21 ` Taylan Ulrich Bayırlı/Kammer
2015-12-07 10:58 ` Taylan Ulrich Bayırlı/Kammer
2015-12-07 14:42 ` Ludovic Courtès
2015-12-08 10:53 ` tomas
2015-12-07 10:28 ` Marko Rauhamaa
2015-12-07 11:15 ` Marko Rauhamaa
2015-12-07 12:44 ` Amirouche Boubekki
2015-12-07 12:52 ` Marko Rauhamaa
2015-12-08 15:39 ` Mark H Weaver
2015-12-08 17:34 ` Marko Rauhamaa
2015-12-08 19:28 ` Chris Vine
2015-12-08 21:51 ` Marko Rauhamaa
2015-12-08 22:02 ` Marko Rauhamaa
2015-12-09 0:52 ` Chris Vine
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=87poyilh8k.fsf@gnu.org \
--to=ludo@gnu.org \
--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).