From: Bruno.Verlyck@inria.fr
To: stein@eecs.harvard.edu
Cc: andrieu@ijm.jussieu.fr, mtucker@eecs.harvard.edu, caml-list@inria.fr
Subject: Re: [Caml-list] Sharing Files between OCaml and C
Date: Wed, 7 Aug 2002 13:40:40 +0200 [thread overview]
Message-ID: <200208071140.g77Bee528601@waco.inria.fr> (raw)
In-Reply-To: <Pine.BSF.4.44.0208061440360.38687-100000@bowser.eecs.harvard.edu> (stein@eecs.harvard.edu)
Date: Tue, 6 Aug 2002 14:50:44 -0400 (EDT)
From: Lex Stein <stein@eecs.harvard.edu>
On POSIX compliant systems, dup() does not, in fact, create a new
vnode for a file. It merely creates a new file descriptor table
entry (in the process's in-kernel descriptor table) that points to
exactly the same vnode. The two descriptors share the same
buffered blocks in the global buffer cache.
The problem I was alluding to is a local (inside the Caml process)
buffering one: the Caml runtime doesn't use C stdio, and has its own
buffering scheme. As the original poster told us about FILE * and
channels, I assumed he would mix I/O on channels and FILE * pointing
to the same file. Then he has to be cautious.
Bruno.
-------------------
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 prev parent reply other threads:[~2002-08-07 11:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-05 9:26 [Caml-list] Matching when Nicolas Cannasse
2002-08-05 9:41 ` Luc Maranget
2002-08-05 16:13 ` John Max Skaller
2002-08-05 19:29 ` Luc Maranget
2002-08-05 20:16 ` [Caml-list] Sharing Files between OCaml and C Michael Tucker
2002-08-06 13:04 ` Olivier Andrieu
2002-08-06 14:01 ` Bruno.Verlyck
2002-08-06 18:50 ` Lex Stein
2002-08-07 11:40 ` Bruno.Verlyck [this message]
2002-08-05 13:05 ` [Caml-list] Matching when Pierre Weis
2002-08-05 15:50 ` John Max Skaller
2002-08-05 16:02 ` Remi VANICAT
2002-08-05 16:23 ` John Max Skaller
2002-08-05 18:25 ` Oleg
2002-08-06 6:37 ` Florian Hars
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=200208071140.g77Bee528601@waco.inria.fr \
--to=bruno.verlyck@inria.fr \
--cc=andrieu@ijm.jussieu.fr \
--cc=caml-list@inria.fr \
--cc=mtucker@eecs.harvard.edu \
--cc=stein@eecs.harvard.edu \
/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