I mean, that may be the best near term fix for our problems. Does require Haskell platform to ship with cabal 1.18, but maybe that approach would fix all the cpp woes for the near term. ESP since most cpp use is in cabalized projects anyways.
On Monday, November 4, 2013, Carter Schonwald wrote:
Maybe we should experiment with it a bit more seriously. With cabal 1.18 it's super easy to tell ghc to call an external program for the cpp pass. And that's our current source of problems.
On Monday, November 4, 2013, Malcolm Wallace wrote:
AFAIK, it is solely the (L)GPL licence issue. GHC central preferred to use/distribute the GPL'd gcc compiler rather than the GPL'd cpphs preprocessor. (No, it made no sense to me either.)
Regards,
Malcolm
On 4 Nov 2013, at 09:40, Herbert Valerio Riedel wrote:
> Hello Malcolm,
>
> On 2013-11-04 at 10:28:27 +0100, Malcolm Wallace wrote:
>> Of course, cpphs solved this problem nearly a decade ago.
>
> Btw, what has been the reason it hasn't been adopted as bundled `cpp`
> replacement in the GHC distribution in the past? (if it remains a
> separate executable, its GPL licence shouldn't be an issue -- after all,
> ghc relies on the gcc executable which is GPL'ed too)
>
> cheers,
> hvr
> _______________________________________________
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://www.haskell.org/mailman/listinfo/ghc-devs
_______________________________________________
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs