From: <tomas@tuxteam.de>
To: guile-devel@gnu.org
Subject: Re: Reading data from a file descriptor
Date: Tue, 17 Nov 2015 14:33:11 +0100 [thread overview]
Message-ID: <20151117133311.GC14674@tuxteam.de> (raw)
In-Reply-To: <20151117135517.42458d6a@bother.homenet>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, Nov 17, 2015 at 01:55:17PM +0000, Chris Vine wrote:
> On Tue, 17 Nov 2015 13:52:21 +0100
> <tomas@tuxteam.de> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On Tue, Nov 17, 2015 at 12:59:56PM +0000, Chris Vine wrote:
> > > On Tue, 17 Nov 2015 10:53:19 +0100
> >
> > [...]
> >
> > > guile's R6RS implementation has get-bytevector-some, which will do
> > > that for you, with unix-read-like behaviour.
> >
> > Thank you a thousand. You made me happy :-)
>
> I suppose it is worth adding that it might not be optimally efficient
> for all uses, as there is no get-bytevector-some! procedure which
> modifies an existing bytevector and takes a maximum length value. I
> guess it is a matter of 'suck it and see', efficiency-wise.
>
> If you are sending/receiving binary packets, it might be better to make
> them of fixed size and use get-bytevector-n!. (Unfortunately,
> get-bytevector-n! does block until n is fulfilled according to R6RS:
> "The get-bytevector-n! procedure reads from binary-input-port, blocking
> as necessary, until count bytes are available from binary-input-port or
> until an end of file is reached".)
:-(
As I noted before, it's a while since I attempted that. I was looking
for an equivalent of read(2) and write(2): simple, efficient, easy to
understand semantics (if you discount the EOF problem for now).
Perhaps the limitations you mention above steered me towards
read-string!/partial and friends, then.
Thanks & regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlZLLJcACgkQBcgs9XrR2kbS9gCeNM696u8KT9Fzq0fSifH8YKa3
VjEAn0KKx5Im4UNxUumiy0RroiKT3iDU
=nAXY
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-11-17 13:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-07 14:52 Reading data from a file descriptor Jan Synáček
2015-11-07 15:16 ` Artyom Poptsov
2015-11-07 15:29 ` Artyom Poptsov
2015-11-07 23:49 ` Andreas Rottmann
2015-11-09 7:25 ` Jan Synáček
2015-11-13 15:51 ` Mark H Weaver
2015-11-13 20:41 ` Jan Synáček
2015-11-13 20:45 ` Thompson, David
2015-11-15 11:09 ` Jan Synáček
2015-11-15 12:05 ` Thompson, David
2015-11-16 10:54 ` Amirouche Boubekki
2015-11-17 9:53 ` tomas
2015-11-17 12:59 ` Chris Vine
2015-11-17 12:52 ` tomas
2015-11-17 13:55 ` Chris Vine
2015-11-17 13:33 ` tomas [this message]
2016-06-20 10:40 ` Andy Wingo
2016-06-20 10:58 ` tomas
2015-11-18 8:28 ` Jan Synáček
2015-11-16 13:02 ` tomas
2015-11-23 21:07 ` Andreas Rottmann
2015-11-24 15:28 ` tomas
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=20151117133311.GC14674@tuxteam.de \
--to=tomas@tuxteam.de \
--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).