Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Aleksey Nogin <nogin@metaprl.org>
To: Vincent Hanquez <tab@snarc.org>
Cc: Richard Jones <rich@annexia.org>,
	caml-list@yquem.inria.fr, omake-devel@metaprl.org
Subject: Re: [Caml-list] Inotify binding
Date: Tue, 28 Nov 2006 22:28:12 -0800	[thread overview]
Message-ID: <456D287C.1020900@metaprl.org> (raw)
In-Reply-To: <20061122001645.GA27158@snarc.org>

On 21.11.2006 16:16, Vincent Hanquez wrote:

> On Tue, Nov 21, 2006 at 11:55:46PM +0000, Richard Jones wrote:
>> On Tue, Nov 21, 2006 at 09:18:34PM +0100, Vincent Hanquez wrote:
>>> I've made a small bindings for inotify, aka linux file system notification
>>> new subsystem.
>> I think OMake includes bindings for gamin.
> 
> it seems to be talking FAM.

Actually, in our LibMojave (which is what OMake uses) we have bindings for:
 - FAM
 - Gamin (using either the generic FAM interface, or taking advantage of
Gamin extensions)
 - kqueue (FreeBSD, OS X)
 - inotify (Linux)
 - ??? (Win32) - not sure what exactly is used there

In all five cases, we provide the _same_ fam-style interface on the
OCaml side. We also have OMake autoconf-style scripts that can detect
which of the fours notification mechanisms is present on a specific
machine and use the appropriate one.

> Sounds more like a bad thing than a good thing to me.
> Direct inotify binding are much smaller/simpler anyway.

That might be true, but only if you happen to be on a machine that
provides inotify. We do utilize inotify if it is present, but we also
have an option of using one of the other four when there is no inotify.

Aleksey


      reply	other threads:[~2006-11-29  6:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-21 20:18 Vincent Hanquez
2006-11-21 23:55 ` [Caml-list] " Richard Jones
2006-11-22  0:16   ` Vincent Hanquez
2006-11-29  6:28     ` Aleksey Nogin [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=456D287C.1020900@metaprl.org \
    --to=nogin@metaprl.org \
    --cc=caml-list@yquem.inria.fr \
    --cc=omake-devel@metaprl.org \
    --cc=rich@annexia.org \
    --cc=tab@snarc.org \
    /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