From: Erik de Castro Lopo <mle+ocaml@mega-nerd.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Buffered input channel
Date: Fri, 3 Aug 2007 07:09:22 +1000 [thread overview]
Message-ID: <20070803070922.c250d137.mle+ocaml@mega-nerd.com> (raw)
In-Reply-To: <200708021651.57115.alexandre.pilkiewicz@polytechnique.org>
Alexandre Pilkiewicz wrote:
> Hi all
>
> I'm currently working on the Harmony project, and I'm looking for a buffered
> access to regular files with four "requested" features :
> input_char
> pos_in
> seek_in
> can be integrated in a project under GPL
Is there anything wong with open_in, input_char, pos_in, seek_in and
close_in of the Pervasives module?
Erik
--
-----------------------------------------------------------------
Erik de Castro Lopo
-----------------------------------------------------------------
"One serious obstacle to the adoption of good programming languages is
the notion that everything has to be sacrificed for speed. In computer
languages as in life, speed kills." -- Mike Vanier
next prev parent reply other threads:[~2007-08-02 21:09 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 ` Erik de Castro Lopo [this message]
2007-08-02 21:46 ` [Caml-list] " Alexandre Pilkiewicz
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=20070803070922.c250d137.mle+ocaml@mega-nerd.com \
--to=mle+ocaml@mega-nerd.com \
--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