From: "Francois Rouaix" <francois@rouaix.org>
To: <caml-list@inria.fr>
Subject: [Caml-list] native threads, connect
Date: Sat, 20 Jul 2002 10:17:11 -0700 [thread overview]
Message-ID: <000e01c23011$4a0c1bc0$ca01a8c0@homebox> (raw)
Hi all,
I'm upgrading some very old network code of mine to Ocaml 3.05,
and I'm getting confused about the behavior of connect() in
bytecode threads vs. native threads.
As you know, to get a yieldable connect, you put a socket
in non-blocking mode, connect, and wait for the socket to
be writable. That is how connect is written in
otherlibs/threads/unix.ml.
Now on the other hand otherlibs/systhreads does not
have a specific unix.ml that defines a connect().
Which unix.ml is used when compiling with -threads with
bytecode and native compilers (with Ocaml configured in native
threads)?
--f
-------------------
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
next reply other threads:[~2002-07-23 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-20 17:17 Francois Rouaix [this message]
2002-07-25 9:07 ` Xavier Leroy
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='000e01c23011$4a0c1bc0$ca01a8c0@homebox' \
--to=francois@rouaix.org \
--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;
as well as URLs for NNTP newsgroup(s).