From: Igor Pechtchanski <pechtcha@cs.nyu.edu>
To: EL CHAAR Rabih SGAM/AI/SAM <RABIH.ELCHAAR@sgam.com>
Cc: Julien Narboux <Julien.Narboux@inria.fr>,
Richard Jones <rich@annexia.org>,
caml-list@yquem.inria.fr
Subject: RE: [Caml-list] The best way to circumvent the lack of Thread.kill ?
Date: Mon, 7 Nov 2005 22:23:27 -0500 (EST) [thread overview]
Message-ID: <Pine.GSO.4.63.0511072221150.847@slinky.cs.nyu.edu> (raw)
In-Reply-To: <7F070E410B10EE419826BF5206322CC20950E0@frdef-exmb01.europe.am.socgen>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1722 bytes --]
On Wed, 2 Nov 2005, EL CHAAR Rabih SGAM/AI/SAM wrote:
> > -----Message d'origine-----
> > De : Julien Narboux
> > Envoyé : mercredi 2 novembre 2005 12:22
> > À : Richard Jones
> > Cc : caml-list@yquem.inria.fr
> > Objet : Re: [Caml-list] The best way to circumvent the lack of
> > Thread.kill ?
> >
> > Richard Jones wrote:
> >
> > >On Wed, Nov 02, 2005 at 10:52:12AM +0100, Julien Narboux wrote:
> > >
> > >
> > >>My problem is that I don't want to pollute my target thread with checks
> > >>for a variable.
> > >>
> > >>Indeed, I am writing a graphical user interface for an automated theorem
> > >>prover.
> > >>
> > >>
> > >
> > >How about forking off the theorem prover as a separate process? You
> > >can communicate the result back to the main program using either a
> > >status code or a pipe (depending on how complex the result structure
> > >is). The interrupt button just kills the forked process.
> > >
> > >Rich.
> >
> > Yes, but the problem is that under the native windows port (see
> > http://caml.inria.fr/pub/docs/manual-ocaml/manual035.html) :
> >
> > "kill, pause not implemented (no inter-process signals in Windows)"
> >
> > Julien Narboux
>
> If i'm not mistaken, fork is not also implemented under windows.
>
> Rabih
It is -- only it's called CreateProcess (and has weird semantics)...
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. /DA
next prev parent reply other threads:[~2005-11-08 3:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 11:33 EL CHAAR Rabih SGAM/AI/SAM
2005-11-08 3:23 ` Igor Pechtchanski [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-02 9:52 Julien Narboux
2005-11-02 10:54 ` [Caml-list] " Richard Jones
2005-11-02 11:22 ` Julien Narboux
2005-11-02 13:00 ` Jacques Garrigue
2005-11-02 12:57 ` Julien Narboux
2005-11-02 13:23 ` Gerd Stolpmann
2005-11-02 14:00 ` Gerd Stolpmann
2005-11-02 14:32 ` Julien Narboux
2005-11-02 15:07 ` Gerd Stolpmann
2005-11-02 14:53 ` David Teller
2005-11-02 16:24 ` Alessandro Baretta
2005-11-02 17:00 ` David Teller
2005-11-02 18:43 ` Alessandro Baretta
2005-11-02 18:29 ` David Teller
2005-11-08 20:36 ` Jonathan Bryant
2005-11-09 1:18 ` Grégory Guyomarc'h
2005-11-09 12:37 ` Richard Jones
[not found] ` <4371A0A6.4010306@laposte.net>
2005-11-09 13:32 ` Jonathan Bryant
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=Pine.GSO.4.63.0511072221150.847@slinky.cs.nyu.edu \
--to=pechtcha@cs.nyu.edu \
--cc=Julien.Narboux@inria.fr \
--cc=RABIH.ELCHAAR@sgam.com \
--cc=caml-list@inria.fr \
--cc=caml-list@yquem.inria.fr \
--cc=rich@annexia.org \
/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