From: Alexandre Pilkiewicz <alexandre.pilkiewicz@polytechnique.org>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Buffered input channel
Date: Thu, 2 Aug 2007 17:46:52 -0400 [thread overview]
Message-ID: <200708021746.52887.alexandre.pilkiewicz@polytechnique.org> (raw)
In-Reply-To: <20070803070922.c250d137.mle+ocaml@mega-nerd.com>
On Thursday 02 August 2007 17:09:22 Erik de Castro Lopo wrote:
> Is there anything wong with open_in, input_char, pos_in, seek_in and
> close_in of the Pervasives module?
Well, I thought the problem was with the buffering, but as Alain made me
realise, the standard input channels are buffered (of size 4096 if I
understand well what I read). The documentation wasn't really clear at this
subject (at least not the description of the Pervasives module), and I had
not enough courage to read the C code of the implementation. I should. So my
very bad performances don't come from there !
Thanks for the very quick answers
Alexandre
next prev parent reply other threads:[~2007-08-02 21:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 20:51 Alexandre Pilkiewicz
2007-08-02 21:09 ` [Caml-list] " Erik de Castro Lopo
2007-08-02 21:46 ` Alexandre Pilkiewicz [this message]
2007-08-02 21:09 ` Alain Frisch
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=200708021746.52887.alexandre.pilkiewicz@polytechnique.org \
--to=alexandre.pilkiewicz@polytechnique.org \
--cc=caml-list@yquem.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