John Meacham wrote:
[...]
also, it would be good if config.h could be renamed to something like
ghc-config.h, because otherwise the conflict between the names can hide
bugs where you get the incorrect config.h or make it tricky to get at
the GHC one if it is actually the one you want.
That's defini
On Mon, Mar 01, 2004 at 11:55:05AM -, Simon Marlow wrote:
> Yes, we should definitely do that. I'm surprised this hasn't caused
> problems before (or maybe it has?).
The reasons it has not been as much of an issue before are twofold as
far as I can tell,
1. cpp only complains if you #define
> The inclusion of the GHC made config.h in HsFFI.h makes it extremely
> difficult to use autoconf with ones own projects without dealing with
> horrible name clashes everywhere. Is there some way this can be fixed?
> perhaps pre-generating the HsFFI.h.
>
> although I don't think it is stated ex
The inclusion of the GHC made config.h in HsFFI.h makes it extremely
difficult to use autoconf with ones own projects without dealing with
horrible name clashes everywhere. Is there some way this can be fixed?
perhaps pre-generating the HsFFI.h.
although I don't think it is stated explicitly by th
