| > the point is that haddock.ghc is using the ghc api, which is | > (a) an internal api, or at least an api to ghc's internals and | > (b) still under rapid development. | | It's an exported, stable, documented and supported API - or at least I | believe that is the eventual intention. | ... | Hopefully, in time, the pain associated with using the GHC API will reduce.
Yes, that *is* the intention! But the GHC API is still something of a historical accident, rather than a carefully-designed artefact in its own right, and Claus is right to say that it's still moving. Simon and I did some work on it last week, but we'd love it if someone with a "client hat" (Neil?!) wanted to look at it as a whole and propose a design. API design is not routine -- it's creative and needs good taste. Simon _______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
