RE: Mailing list (was: Re: Q: Threads in GHC's RTS)

1999-04-14 Thread Simon Marlow
Sven writes: P.S.: Something completely unrelated: Why is majordomo.haskell.org expanded to scarlet.cam.uk.eu.microsoft.com in the To:-field? IMHO this is a bad idea, e.g. when people cut-and-paste this into their address books and scarlet is renamed to e.g.

Mailing list (was: Re: Q: Threads in GHC's RTS)

1999-04-13 Thread Keith Wansbrough
Sven writes: P.S.: Something completely unrelated: Why is majordomo.haskell.org expanded to scarlet.cam.uk.eu.microsoft.com in the To:-field? IMHO this is a bad idea, e.g. when people cut-and-paste this into their address books and scarlet is renamed to e.g. rhett. :-)

RE: Q: Threads in GHC's RTS

1999-04-13 Thread Simon Peyton-Jones
Panne [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 13, 1999 10:09 AM To: GHC Users Subject: Re: Q: Threads in GHC's RTS "Sigbjorn Finne (Intl Vendor)" wrote: [...]Good point, I've committed a fix for this. Adjustor.c gets more and more impressive. :-) BTW: What is the

RE: Q: Threads in GHC's RTS

1999-04-09 Thread Sigbjorn Finne (Intl Vendor)
Sven Panne [EMAIL PROTECTED] writes: [...] Aaaah! *lights going on* But then I suggest that foreign export dynamic should be changed to return a stable pointer instead of an Addr. This shouldn't break too much code, because both are CCallable. I don't see the need, since (deep

Re: Q: Threads in GHC's RTS

1999-04-09 Thread Sven Panne
Simon Peyton-Jones wrote: Yes, we do this a lot. It's such a useful thing that I wonder whether we should support it more directly, somehow. That eases my mind. :-) I feared that I'm the only one doing this kind of hackery... As it stands, its vulnerable to 'blockingSem' getting inlined

Re: Q: Threads in GHC's RTS

1999-04-09 Thread Sven Panne
"Manuel M. T. Chakravarty" wrote: [...] The required synchronization could of course be programmed using `Concurrent's semaphores, but with the disadvantage that if we want to provide this thread-safety transparently for user applications in a library, we have to define a "new" IO monad on