From: "Jonathan Roewen" <jonathan.roewen@gmail.com>
To: "Nathaniel Gray" <n8gray@gmail.com>
Cc: "Caml Mailing List" <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] Re: Select on channels (again)
Date: Tue, 22 Aug 2006 12:42:07 +1200 [thread overview]
Message-ID: <ad8cfe7e0608211742g6bb29ad6i9d13d5f07abafe27@mail.gmail.com> (raw)
In-Reply-To: <aee06c9e0608211547o6130050aq70a265cc1f50611d@mail.gmail.com>
Why can't you just use the unix file opening functions since you're
using unix select? And if you need the ocaml in/out channels, convert
the unix file descriptors to ocaml ones instead of the other way
around. Seems simple enough to me.
On 8/22/06, Nathaniel Gray <n8gray@gmail.com> wrote:
> Tap... tap...
>
> Hello? Is this thing on?
>
> On 8/14/06, Nathaniel Gray <n8gray@gmail.com> wrote:
> > Like others before me, I'm hitting the frustrating limitation that
> > it's impossible to select on a channel. This limitation forces one to
> > reimplement buffered IO in many situations where using channels would
> > otherwise be easy and sensible. There has been discussion on this
> > list in the past about this limitation[1], and there have been two
> > requests filed in mantis for this feature[2,3], but the ocaml dev team
> > has been silent on the matter. Is this feature objectionable to the
> > dev team or is it just a case of "too much work, not enough time?" If
> > somebody was to submit a quality patch implementing the feature would
> > it be accepted?
> >
> > Cheers,
> > -n8
> >
> > [1] <http://caml.inria.fr/pub/ml-archives/caml-list/2005/03/8aae2e3c54cfb976fe52664ab1c84994.en.html>
> > [2] <http://caml.inria.fr/mantis/view.php?id=3075>
> > [3] <http://caml.inria.fr/mantis/view.php?id=3579>
> >
> > --
> > >>>-- Nathaniel Gray -- Caltech Computer Science ------>
> > >>>-- Mojave Project -- http://mojave.cs.caltech.edu -->
> >
>
>
> --
> >>>-- Nathaniel Gray -- Caltech Computer Science ------>
> >>>-- Mojave Project -- http://mojave.cs.caltech.edu -->
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
next prev parent reply other threads:[~2006-08-22 0:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 0:46 Nathaniel Gray
2006-08-21 22:47 ` Nathaniel Gray
2006-08-22 0:42 ` Jonathan Roewen [this message]
2006-08-22 6:27 ` [Caml-list] " Nathaniel Gray
2006-08-22 6:41 ` Jonathan Roewen
2006-08-22 8:15 ` skaller
2006-08-22 21:15 ` Mike Lin
2006-08-23 5:12 ` Nathaniel Gray
2006-08-22 8:10 ` Olivier Andrieu
2006-08-23 5:27 ` Nathaniel Gray
2006-08-22 8:21 ` Jacques Garrigue
2006-08-23 5:16 ` Nathaniel Gray
2006-08-23 6:35 ` skaller
2006-08-23 19:31 ` Nathaniel Gray
2006-08-24 5:37 ` skaller
2006-08-24 19:06 ` Nathaniel Gray
2006-08-25 1:55 ` skaller
2006-08-25 22:19 ` Nathaniel Gray
2006-08-23 8:29 Christoph Bauer
2006-08-23 17:35 ` Robert Roessler
2006-08-24 8:18 ` Robert Roessler
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=ad8cfe7e0608211742g6bb29ad6i9d13d5f07abafe27@mail.gmail.com \
--to=jonathan.roewen@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=n8gray@gmail.com \
/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