Consider this:
module M (Monoid(..)) where { import Control.Monad.Monoid; }
I'd like Haddock to show documentation for Monoid in module M (for instance).
Unfortunately this isn't possible. Haddock can produce documentation with hyperlinks to entities in another package, but it cannot include full documentation for entities which are re-expored from a different package. This would require essentially keeping a copy of the entire documentation for the package in the interface file.
Are there standard Haddock-interfaces for the standard libraries?
A GHC distribution comes with Haddock interfaces for all the packages that it ships with. Cheers, Simon
In article
<3429668D0E777A499EE74A7952C382D10146A9DA@EUR-MSG-01.europe.corp.microso
ft.com>,
"Simon Marlow"
Unfortunately this isn't possible. Haddock can produce documentation with hyperlinks to entities in another package, but it cannot include full documentation for entities which are re-expored from a different package. This would require essentially keeping a copy of the entire documentation for the package in the interface file.
So what is stored in a Haddock interface file?
Are there standard Haddock-interfaces for the standard libraries?
A GHC distribution comes with Haddock interfaces for all the packages that it ships with.
Where? In the Debian package ghc 6.2-0.woody.1 I can only find the .hi files, and that's not the same thing, is it? -- Ashley Yakeley, Seattle WA
participants (2)
-
Ashley Yakeley -
Simon Marlow