Claus Reinke wrote:
However, until this fundamental issue is addressed, is there any
way to make GHC Api clients less dependent on the details of a specific
GHC Api version? In the scenario given above, if T,
despite being built with GHC V1, was able to work with GHC
V2's Api, then it could use GHC V2's formats describing the
libraries/packages needed by H. But that means (a) abstraction
from the rapidly changing GHC Api, to get a stable sub-interface,
I wonder if Template Haskell provides this already, in some form?
Perhaps it would need to be extended, even to allow you to break
abstraction (so that while type-functions are in flux, and we aren't
ready to add them to the stable TH API, Haddock could consciously use
ifdefs or something to get at the specific GHC 6.10 representation).
I'm sure there are all kinds of problems with this idea, including that
TH isn't actually entirely stable! and it might be impossible. -- but if
it's useful then TH would get some more love, which could make its
existing clients happier too...
-Isaac
_______________________________________________
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listinfo/cvs-ghc
