From: Nicolas George <nicolas.george@ens.fr>
To: caml-list@inria.fr
Subject: [Caml-list] UNIX_BUFFER_SIZE
Date: Fri, 6 Jun 2003 21:39:03 +0200 [thread overview]
Message-ID: <20030606193903.GA28852@clipper.ens.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 456 bytes --]
May I suggest that the documentation for Unix.read, Unix.write,
Unix.send and Unix.recv will not handle more than UNIX_BUFFER_SIZE ==
16kb at once?
I know it is a mistake to assume that a single call will read or write
as much data as requested even on regular files far from EOF (but most
of the time, that workd!), but this may also prevent programmers from
trying to have larger buffers.
--
:'-( NNTP Yaf did crash today because of that
[-- Attachment #2: Type: application/pgp-signature, Size: 185 bytes --]
reply other threads:[~2003-06-06 19:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030606193903.GA28852@clipper.ens.fr \
--to=nicolas.george@ens.fr \
--cc=caml-list@inria.fr \
/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 NNTP newsgroup(s).