you are right that i need to fix the FFI problems.
but coming back to the threading stuff i do in my haskell code: do i
really need to use the threaded runtime here?
from the ghc-docs for the -threaded flag:
Note that you do not need -threaded in order to use concurrency; the
single-threaded
after reading in GHC's implementation of concurrency and even more
important in the documentation of hWaitForInput it seems clear that my
receiver thread blocks and the sender cannot be executed:
NOTE for GHC users: unless you use the -threaded flag, hWaitForInput
t where t = 0 will block all
On Thu, Mar 24, 2011 at 9:53 AM, oliver mueller
oliver.muel...@gmail.com wrote:
if anybody knows of a better way please let me know!
I'd recommending trying to fix your obscure FFI problems re: the
threaded RTS and go back to using that. Switching concurrency off
altogether is a curious response
hello,
i'm a bit lost here so i hope s.o. can help me here:
seems i have a problem in my code when compiled with ghc-7.0.2:
what i try to do:
serverside:
-listen on a socket and reply to requests
client-side:
-send a request to that server
-wait for a response (with a timeout)
any ideas on how i
