From: Francois Rouaix <frouaix@liquidmarket.com>
To: Don Syme <dsyme@microsoft.com>
Cc: caml-list@inria.fr
Subject: Re: threads & OCamlTK
Date: Tue, 16 Mar 1999 09:18:01 -0800 [thread overview]
Message-ID: <199903161715.JAA04021@fiji01.liquidmarket.com> (raw)
In-Reply-To: Your message of "Mon, 15 Mar 1999 07:05:21 PST." <39ADCF833E74D111A2D700805F1951EF0F00BA6B@RED-MSG-06>
> And, on a vaguely related topic, is it possible to use threads with programs
> that also use OCamlTK? I know Tk is not threadsafe, but if only one thread
> is calling Tk functions, then perhaps it's still OK?
Yes, it should be ok. But this also includes the Tk event loop, and thus
all callbacks. Also, there is the issue of using Thread primitives within
a callback (e.g. having the callback on a button triggering a condition).
In bytecode threads, this will probably not work.
Jun and I discussed these issues a long time ago, and Jun implemented
a modified version of the CamlTK core where the event loop would be handled
in Caml instead of C, so as to be compatible with threads, to some extent
(all other Tk calls still need to be in a critical section).
I don't think we ever distributed this version, and I'm not even sure it
would work on Windows, but you might want to check with Jun.
--f
next prev parent reply other threads:[~1999-03-16 17:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-15 15:05 Don Syme
1999-03-16 17:18 ` Francois Rouaix [this message]
1999-03-16 17:42 ` Jun P. Furuse
1999-03-22 18:39 ` Trevor Jim
1999-03-22 20:04 ` William Chesters
1999-03-23 16:08 ` Xavier Leroy
1999-03-23 15:07 ` Jerome Vouillon
1999-03-24 17:27 ` William Chesters
1999-03-16 17:32 William Chesters
1999-03-17 15:02 Don Syme
1999-03-17 15:57 ` William Chesters
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=199903161715.JAA04021@fiji01.liquidmarket.com \
--to=frouaix@liquidmarket.com \
--cc=caml-list@inria.fr \
--cc=dsyme@microsoft.com \
/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