Re: RFC: Does it make sense to build a ocaml-eventfd package?
- To: ygrek <firstname.lastname@example.org>
- Cc: email@example.com
- Subject: Re: RFC: Does it make sense to build a ocaml-eventfd package?
- From: Goswin von Brederlow <firstname.lastname@example.org>
- Date: Tue, 14 Sep 2010 21:27:45 +0200
- Message-id: <email@example.com>
- In-reply-to: <firstname.lastname@example.org> (email@example.com's message of "Sun, 29 Aug 2010 22:30:27 +0300")
- References: <firstname.lastname@example.org> <email@example.com> <4C77A121.firstname.lastname@example.org> <email@example.com>
ygrek <firstname.lastname@example.org> writes:
> On Fri, 27 Aug 2010 13:27:29 +0200
> StÃ©phane Glondu <email@example.com> wrote:
>> This is a very good idea! There was also a discussion about crypt()
>> recently, which is also too trivial to be packaged by itself.
>> Beware that eventfd is Linux-specific. The hypothetic project should
>> somehow cope with non-Linux platforms.
> Ok, here we go : http://extunix.forge.ocamlcore.org/
> Pushed some existing bindings, custom configure, camlp4 extension to
> generate two modules from single source : "full" (functions not available for
> the platform will throw Invalid_argument, as Unix) and "specific" (only includes
> functions found during configure step).
> Feel free to contribute and criticize. :)
Should we have an ExtUnix.Linux submodule for eventfd and signalfd?
let eventfd () = throw ENOSYS
on platforms that don't have it?
I could imagine emulating the eventfd with pipes but signalfd might be
impossible to emulate.