> Simon Marlow wrote:
>
> > What's wrong with just saying -I whenever you say -i?
>
> This seems to work but for more complicated combinations the
> two options have slightly
> different formats. For example, if I have several
> directories separated by colons, and
> end the list with a sup
Simon Marlow wrote:
> What's wrong with just saying -I whenever you say -i?
This seems to work but for more complicated combinations the two options have slightly
different formats. For example, if I have several directories separated by colons, and
end the list with a superfluous colon (which
> Thanks to ghc --make it is now common to compile files from a
> different directory.
> This creates a new problem, in that if a file starts with a
> {-# include #-}
> directive, ghc will try to find c-header.h in the current
> directory, not in the directory
> containing the source file. S
Thanks to ghc --make it is now common to compile files from a different directory.
This creates a new problem, in that if a file starts with a
{-# include #-}
directive, ghc will try to find c-header.h in the current directory, not in the
directory
containing the source file. So we need a way