> >This might work, but no guarantees.
>
> OK, so I'd be better off making sure all Haskell runs in one
> OS-thread.
My concerns still apply - non-thread-friendly library calls may mean
that GHC's RTS interacts badly with the rest of your threaded program.
> Although presumably I can use Haske
At 2001-10-25 03:12, Simon Marlow wrote:
>This might work, but no guarantees.
OK, so I'd be better off making sure all Haskell runs in one OS-thread.
Although presumably I can use Haskell-threads: I can have a special
Haskell-thread that handled a queue of incoming execution requests,
firing
> >It isn't safe to call foreign exported
> >functions from more that one OS thread simultaneously.
>
> OK, can I call a foreign exported function from some other
> thread while
> the main thread is in 'foreign import' native code? I could
> have calls to
> the foreign exported function block
At 2001-10-24 02:52, Simon Marlow wrote:
>If you're talking about OS threads (eg. POSIX threads),
Yes
>then GHC's RTS certainly isn't thread safe.
Good. This means I know why it's crashing...
>It isn't safe to call foreign exported
>functions from more that one OS thread simultaneously.
O
> Is there a way of calling exported 'dynamic export' functions in a
> thread-safe manner? I have this problem in JVM-Bridge...
>
> This is what the main thread does, from Haskell:
>
> 1. starts the Java VM, which starts a bunch of other threads,
> including
> the AWT thread;
> 2. creates a
