From: Alexandre Frey <frey@paris.ensmp.fr>
To: Bruno.Verlyck@inria.fr
Cc: caml-list@inria.fr
Subject: Re: Objective Caml's Unix libraries
Date: Thu, 13 Mar 97 10:52 MET [thread overview]
Message-ID: <m0w57Bp-0009bVC@toxic.ensmp.fr> (raw)
In-Reply-To: <199703121950.UAA13512@kickapoo.inria.fr> (Bruno.Verlyck@inria.fr)
Bruno,
> In english: Xavier's arguments are very strong. But within them (and
> the Unix library), I can't write a /bin/sh clone, because of >&3
> (here, and for Pawel.Wojciechowski, it would be enough to add a fun
> fileno : filedesc -> int, like the stdio macro) and <&3 -- but I
> thought about it for only 5 min.
As a hack, you can always write this:
let fileno (fd: file_descr): int = (Obj.magic fd)
But of course, you loose the safety of the abstract `file_descr' type.
--
Alexandre.
prev parent reply other threads:[~1997-03-13 13:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-03-11 23:05 Pawel Wojciechowski
1997-03-12 9:41 ` Xavier Leroy
1997-03-12 19:50 ` Bruno.Verlyck
1997-03-13 9:52 ` Alexandre Frey [this message]
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=m0w57Bp-0009bVC@toxic.ensmp.fr \
--to=frey@paris.ensmp.fr \
--cc=Alexandre.Frey@ensmp.fr \
--cc=Bruno.Verlyck@inria.fr \
--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).