From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: caml-list@inria.fr
Subject: [Caml-list] unbuffered input
Date: Thu, 21 Aug 2003 12:11:57 -0400 [thread overview]
Message-ID: <20030821161157.GH18587@alan-schm1p> (raw)
Hi,
I've been looking at this for about one hour, and I seem to get stuck:
how can I do unbuffered input in caml ? I want a program to block until
a char is entered. I tried input_char and Unix.read (without
and with Unix.select), to no avail. I do not know if it is caml, the
libc, or the terminal that is buffering.
Any hint on how to do this ?
Thanks a lot,
Alan Schmitt
--
The hacker: someone who figured things out and made something cool happen.
-------------------
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
next reply other threads:[~2003-08-21 16:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-21 16:11 Alan Schmitt [this message]
2003-08-21 16:40 ` Michal Moskal
2003-08-21 16:47 ` art yerkes
2003-08-21 16:49 ` [Caml-list] unbuffered input: a solution Alan Schmitt
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=20030821161157.GH18587@alan-schm1p \
--to=alan.schmitt@polytechnique.org \
--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).