From: Stefano Zacchiroli <zack@bononia.it>
To: Inria Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml signal handlers (Sys.signal) and C code
Date: Fri, 18 Apr 2003 20:04:33 +0200 [thread overview]
Message-ID: <20030418180433.GA10194@lordsoth.takhisis.org> (raw)
In-Reply-To: <20030416211607.B30839@pauillac.inria.fr>
On Wed, Apr 16, 2003 at 09:16:07PM +0200, Xavier Leroy wrote:
> enter_blocking_section();
> /* call C functions */
> leave_blocking_section();
Ok, thanks Xavier and Damien for the answers.
Let's go to the next level:
1) {enter,leave}_blocking_section are defined in byterun/signal.{h,c}
and shipped inside libcamlruntime.a. The problem is that signal.h
isn't shipped in the standard ocaml includes, I can obviously trick
the C compiler, but is this the intended behaviour?
2) looking at otherlibs/unix/connect.c I see this block of code:
enter_blocking_section();
retcode = connect(Int_val(socket), &addr.s_gen, addr_len);
leave_blocking_section();
Int_val is used inside the blocking section. I guess that this is
safe because integers aren't heap allocated. Tell me if I'm wrong.
Cheers.
--
Stefano Zacchiroli -- Master in Computer Science @ Uni. Bologna, Italy
zack@{cs.unibo.it,debian.org,bononia.it} - http://www.bononia.it/zack/
" I know you believe you understood what you think I said, but I am not
sure you realize that what you heard is not what I meant! " -- G.Romney
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
prev parent reply other threads:[~2003-04-18 18:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-04 16:56 Stefano Zacchiroli
2003-04-16 19:16 ` Xavier Leroy
2003-04-18 8:41 ` Stefano Zacchiroli
2003-04-18 13:02 ` Damien Doligez
2003-04-18 18:04 ` Stefano Zacchiroli [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=20030418180433.GA10194@lordsoth.takhisis.org \
--to=zack@bononia.it \
--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