caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Keith Wansbrough <Keith.Wansbrough@cl.cam.ac.uk>
To: janne@hybrid.fi
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Unix module and threads
Date: Mon, 06 Sep 2004 10:07:38 +0100	[thread overview]
Message-ID: <E1C4FTP-0006PY-00@mta1.cl.cam.ac.uk> (raw)
In-Reply-To: Your message of "Sun, 05 Sep 2004 16:53:22 +0300." <413B1A52.8060007@hybrid.fi>

Janne Hellsten <janne@hybrid.fi> writes:

> Thank you Markus and David, this is sort of what I was afraid of (e.g., 
> curdir is shared among threads). Thank you for clarifying this.
> 
> As my build scripts require the working directory to be set, I think I 
> have to work-around this and do something along the lines of:
> 
>     Unix.system "cd my_working_dir && build_cmd"
> 
> I wonder if there's some other way of doing this portably and in a 
> thread-safe fashion?

Instead of using Unix.system, do a fork()-and-exec() (as Unix.system
presumably does under the hood), and set the current directory in the
child process after the fork and before the exec.  Take a look at the
implementation of Unix.system in otherlibs/unix/unix.ml to see what I
mean.

--KW 8-)

-------------------
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


  parent reply	other threads:[~2004-09-06  9:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-05  8:00 Janne Hellsten
2004-09-05 13:32 ` David Brown
2004-09-05 13:42 ` Markus Mottl
2004-09-05 13:53   ` Janne Hellsten
2004-09-05 15:27     ` skaller
2004-09-06  9:07     ` Keith Wansbrough [this message]
2004-09-05 13:57   ` Daniel Andor
2004-09-05 15:12   ` skaller

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=E1C4FTP-0006PY-00@mta1.cl.cam.ac.uk \
    --to=keith.wansbrough@cl.cam.ac.uk \
    --cc=caml-list@inria.fr \
    --cc=janne@hybrid.fi \
    /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).