[Haskell-cafe] code-build-test cycle

[Job Vranish]

Yeah linking in windows is _very_ slow. Supposedly this is because the
linker forks a lot of processes. In linux this is fine as forking is dirt
cheap, but in windows (at least older versions, not completely sure about
vista or 7) forking is expensive.

Building a Qt app on my EEE in linux only takes a couple seconds. Building
in windows on my dual core 3.2Ghz machine takes 15-30 seconds.  It's pretty
sad.

I second Bulat's suggestion. If you can compile everything and just use ghci
to avoid the link you should be able to get the best of both works.

- Job


On Fri, Sep 18, 2009 at 12:34 AM, Bulat Ziganshin <bulat.ziganshin at gmail.com
> wrote:

> Hello Michael,
>
> Friday, September 18, 2009, 6:42:32 AM, you wrote:
>
> > Now I'm wondering if Hugs is a faster interpreter.
>
> 2x slower, and incompatib;e with qtHaskell
>
> > meaningful way without compilation. Any advice welcome. Maybe there is a
> > way to speed up the interpretation.
>
> if compilation is fast and only linking is slow, you may recompile
> haskell modules every time but use ghci to omit linking. just execute ghc
> compilation command inside ghci before running your app
>
>
> --
> Best regards,
>  Bulat                            mailto:Bulat.Ziganshin at gmail.com
>
> _______________________________________________
> Haskell-Cafe mailing list
> Haskell-Cafe at haskell.org
> http://www.haskell.org/mailman/listinfo/haskell-cafe
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.haskell.org/pipermail/haskell-cafe/attachments/20090918/c048af57/attachment.html