Alastair Reid wrote/a ecrit/skrev:
> > * import-chasing as part of the spec
>
> This is an environment feature not a language feature.
>
> What does it mean for GHC?
> Are you wanting to do away with Makefiles?
> Makefiles can do an awful lot more than import chasing can
> and GNU makefiles are very, very short in the normal case.
I use a lot of Makefiles, but why must we use ugly tools with beatiful
languages? They are especially bad for a novice, just trying to gain
a little more speed on his Hugs program.
What I'd really like to do is just: ``ghc Main.hs'', and obtain a Main
executable. For the more advance user (using Green-Card, Happy, and
whatnot) there should always be the brainless "C-style" way. I fail
to see why GHC must be so difficult to use for multi file programs(*).
/Tommy
(*): I'm perfectly willing to accept that I'm a clueless newbie, but
even after having read the manual and studied the code, I wasn't able
to get a working Makefile. Is it doable in a few easy steps? Mind
you, that ``ghc -M'' did not cut it: the default rules weren't
specified.
