Hi
Is there some reason you need to run GHCi as a separate process? By doing so, you constrain yourself to communicating with it using inter-process communication (like pipes). Maybe signals too.. but that becomes jolly tricky when you want to port across platforms.
In my case I'd like to work against something which is a bit more stable, keep the binary size small, and interface with Hugs and GHC as well as GHCi, which means I'd have to do the inter-process stuff anyway. Also its not actually that hard in Haskell, no need for pipes, runInteractiveProcess gives you most of what you need. However, using an API is generally a better alternative to prodding a console!
I think that'd be a lot easier. If you want to maintain responsiveness of the GUI, when kicking off an evaluation that uses lots of time, you can use Haskell threads.
That might have issues under Gtk2Hs, see http://haskell.org/gtk2hs/archives/2005/07/24/writing-multi-threaded-guis/ Thanks Neil _______________________________________________ Cvs-ghc mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/cvs-ghc
