From: "Yaron M. Minsky" <yminsky@CS.Cornell.EDU>
To: Caml List <caml-list@inria.fr>
Subject: [Caml-list] really_input and non-blocking operations
Date: 22 Nov 2002 10:29:19 -0500 [thread overview]
Message-ID: <1037978958.12207.26.camel@dragonfly.localdomain> (raw)
I just noticed that it's not safe to use really_input with nonblocking
operations. In particular, as is clear from the source, if really_input
fails in the middle of a read due to a Sys_blocked_io, it ends up
discarding the what it's read so far. It seems like this should be
noted in the documentation.
Another documentation problem: the docs susggest that various unix
errors will be thrown on blocked IO, but in my own experiments, the only
exception I've seen thrown is Sys_blocked_io, which is not as far as I
can tell mentioned anywhere in the docs.
y
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
reply other threads:[~2002-11-22 15:29 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=1037978958.12207.26.camel@dragonfly.localdomain \
--to=yminsky@cs.cornell.edu \
--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).