The pragma

{-# OPTIONS_HADDOCK hide #-}

does what I want, but it seems to me that cabal should be handling this.

On Tue, Mar 30, 2010 at 2:55 PM, Ashish Agarwal <agarwal1975@gmail.com> wrote:
I'm using cabal to build and install a new library I'm writing. In the .cabal file I've exposed only a single module. However, the haddock generated documentation includes even the non-exposed modules, which is not what I want since end-users should not see these. Is there a way to tell cabal to build documentation only for exposed modules?