RE: Haddock warnings for unresolved prelude functions
I'm using Haddock 0.5, compiled for GHC 6.0.1, and I get warnings when "haddock"ing a simple module:
Warning: module not found: Prelude Warning: MyModule: the following names could not be resolved: Prelude.[] Bool Eq
I can see what's happening: I'm not passing Prelude.hs to Haddock, but I'm using pPrelude functions. But I don't want to pass it a Prelude.hs and don't want the warnings either. Is there any way to force it to be silent about unresolved Prelude functions?
There isn't a way to make it silent, unfortunately (maybe I'll add one). These warnings are harmless - they just indicate that Haddock couldn't find the right place to link to for these Prelude types. If you want to generate the hyperlinks, then you need the .haddock file for the base package, which is distributed with GHC, and pass the --read-interface flag to Haddock (see the docs for details). Cheers, Simon
On Mon, 20 Oct 2003 16:25:50 +0100, "Simon Marlow"
There isn't a way to make it silent, unfortunately (maybe I'll add one).
That'd be great.
These warnings are harmless - they just indicate that Haddock couldn't find the right place to link to for these Prelude types.
Yeah, I know. But Prelude "false warnings" could hide more useful warnings.
If you want to generate the hyperlinks, then you need the .haddock file for the base package, which is distributed with GHC, and pass the --read-interface flag to Haddock (see the docs for details).
Nice, I had overlooked that. I'm still getting these two: Warning: Local.Numeric: the following names could not be resolved: Prelude.[] Warning: Local.List: the following names could not be resolved: Prelude.[] but the linking to the standard docs is cool :) /L/e/k/t/u
participants (2)
-
Juanma Barranquero -
Simon Marlow