Re: [Chicken-users] google summer of code

[Ivan Raikov]

"Graham Fawcett" <address@hidden> writes:

> On reflection, I'd much rather see a really efficient IPC system like
> this, rather than having a native-threaded Chicken. 

  Try the MPI egg! (Yet another shameless plug, I know).

>
> Other than for concurrent designs, I think there is a case for native
> threads when I/O is involved. I believe that GHC Haskell uses a
> separate native thread for handling I/O, but (unless you use forkIO)
> runs everything else in lightweight threads. Perhaps we could play a
> similar game, and spawn native threads as I/O custodians, managed
> under a very strict protocol that avoids GC contention and other
> concurrency issues. Perhaps one I/O thread and select/epoll is enough.

  No, forkIO is normally for lightweight threads. forkOS explicitly
associates Haskell threads with native threads. See here for details:

http://www.haskell.org/ghc/docs/latest/html/libraries/base/Control-Concurrent.html#osthreads

  Concurrent Haskell is based on monadic processes: if you want to
have Haskell-like threads, first you need to provide support for
monads in the core of Chicken.

   -Ivan