So here's what I don't understand: we make a non-blocking call to
gtk+'s
main loop
So far, so good.
(which makes a blocking call in a new OS thread).
With (the current version of) GHC's threaded RTS, there's only one OS
thread involved until you spawn a second thread (with forkIO or
forkOS).
S
On Wed, 2004-05-05 at 14:55, Simon Peyton-Jones wrote:
> | I'm thinking about how to make threaded Haskell program work nicely
> with Gtk+ (the widget toolkit) and whether the new threaded rts will
> help or not.
> | Would bound threads help? I'm not sure I understand the idea very
> well.
>
> Tha
| I'm thinking about how to make threaded Haskell program work nicely
with
| Gtk+ (the widget toolkit) and whether the new threaded rts will help
or
| not.
|
...
|
| Would bound threads help? I'm not sure I understand the idea very
well.
That's *exactly* what the bound-threads idea is for. It's
All,
I'm thinking about how to make threaded Haskell program work nicely with
Gtk+ (the widget toolkit) and whether the new threaded rts will help or
not.
Graphics toolkits (X windows or win32 GDI) typically have pretty strict
requirements on threads. While it is possible to make use of multiple
