caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: oliver <oliver@first.in-berlin.de>
To: Gabriel Kerneis <kerneis@pps.jussieu.fr>
Cc: Jeremie Dimino <jdimino@janestreet.com>,
	caml-list@inria.fr, ocsigen@inria.fr
Subject: Re: [Caml-list] BUG in unix.ml (was: strange errors when linking lwt.unix)
Date: Fri, 15 Mar 2013 17:25:28 +0100	[thread overview]
Message-ID: <20130315162528.GC5664@siouxsie> (raw)
In-Reply-To: <20130315161240.GD6473@kerneis.info>

On Fri, Mar 15, 2013 at 04:12:41PM +0000, Gabriel Kerneis wrote:
> Oliver,
> 
> On Fri, Mar 15, 2013 at 05:00:45PM +0100, oliver wrote:
> > The problem occures when using the signal handler from Sys,
> > not from unix module.
> 
> Could you please (at least) read the documentation before contributing to this
> thread again?
> 
> > It was stated that the unix module is doing things wrong.
> > But the Unix signalling mechanism was not used.
> 
> Let me quote it for you:
> 
>   ### Signals ###
>   Note: installation of signal handlers is performed via the functions
>   Sys.signal and Sys.set_signal.
>   -- http://caml.inria.fr/pub/docs/manual-ocaml/libref/Unix.html#6_Signals

OK, I was wrong here.
I had in mind there was a sigaction-function in Unix module also.

My fault, should better have looked it up again, after so long not
using it.

My apologies too Dimino.
Didn't saw what you wanted to point me too.


> 
> So the Unix module does not provide any way to setup a signal handler.  You have
> to use Sys.  Your requirement of demonstrating the issue using Unix only is
> silly.  Period.


Hahah, people say I'm rude and they are themselves.
Welcome in the club. :)


Ciao,
   Oliver

  reply	other threads:[~2013-03-15 16:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAMu2m2Lt8oty_2mEQq8H1oV0-1Rjrf10ai543me9YxB1Nb5xfg@mail.gmail.com>
     [not found] ` <CALScVY=c1M=HAqMeM7x4QrxDTZsn0rB=HcTsQYheYUOBSBFRUQ@mail.gmail.com>
     [not found]   ` <CALScVYnt-m-dRR41rBPo5R3xDx-81tMwBFbM3q+5p4gRqsQC9w@mail.gmail.com>
     [not found]     ` <CALScVYmU7zEXbgdS21gGrq8iFvgVs0FWieKipRE9WtOM+PxeEg@mail.gmail.com>
2013-03-15  9:18       ` Florian Hars
2013-03-15 10:02         ` oliver
2013-03-15 10:11           ` David House
2013-03-15 11:38         ` Jeremie Dimino
2013-03-15 12:43           ` oliver
2013-03-15 13:17             ` Jeremie Dimino
2013-03-15 13:28               ` oliver
2013-03-15 13:43                 ` Jeremie Dimino
2013-03-15 13:24             ` Jeremie Dimino
2013-03-15 13:58               ` oliver
2013-03-15 14:05                 ` oliver
2013-03-15 14:16                   ` Jeremie Dimino
2013-03-15 14:18                     ` oliver
2013-03-15 14:17               ` oliver
2013-03-15 14:27                 ` oliver
2013-03-15 15:05                   ` Jeremie Dimino
2013-03-15 15:11                     ` oliver
2013-03-15 15:44                       ` Gabriel Kerneis
2013-03-15 16:00                         ` oliver
2013-03-15 16:12                           ` Gabriel Kerneis
2013-03-15 16:25                             ` oliver [this message]
2013-03-15 17:28                               ` Jeremie Dimino
2013-03-15 15:16                     ` oliver

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=20130315162528.GC5664@siouxsie \
    --to=oliver@first.in-berlin.de \
    --cc=caml-list@inria.fr \
    --cc=jdimino@janestreet.com \
    --cc=kerneis@pps.jussieu.fr \
    --cc=ocsigen@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).