The haddock package

[Tags: bsd3, program]

Haddock is a documentation-generation tool for Haskell libraries

[Skip to ReadMe]


Versions0.8, 0.9,, 2.1.0, 2.2.0, 2.2.1, 2.2.2, 2.4.0, 2.4.1, 2.4.2, 2.5.0, 2.6.0, 2.6.1, 2.7.0, 2.7.1, 2.7.2, 2.8.0, 2.8.1, 2.9.0, 2.9.1, 2.9.2, 2.9.3, 2.9.4, 2.10.0, 2.11.0, 2.11.1, 2.12.0, 2.13.0, 2.13.1, 2.13.2,, 2.14.1, 2.14.2, 2.14.3, 2.15.0,,, 2.16.0, 2.16.1
Change logCHANGES
Dependenciesbase (>=4.3 && <4.9), haddock-api (==2.16.*) [details]
Copyright(c) Simon Marlow, David Waern
AuthorSimon Marlow, David Waern
MaintainerSimon Hengel <>, Mateusz Kowalczyk <>
Home page
Bug tracker
Source repositoryhead: git clone
UploadedWed Jul 22 21:01:39 UTC 2015 by MateuszKowalczyk
DistributionsDebian:2.13.1, Fedora:2.14.3, FreeBSD:2.16.1, NixOS:2.16.1
Downloads42549 total (717 in last 30 days)
0 []
StatusDocs not available [build log]
Last success reported on 2015-09-29 [all 3 reports]


in-ghc-treeAre we in a GHC tree?DisabledManual

Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info


Maintainers' corner

For package maintainers and hackage trustees

Readme for haddock-2.16.1

# Haddock, a Haskell Documentation Tool

#### About haddock

This is Haddock, a tool for automatically generating documentation
from annotated Haskell source code.  It is primary intended for
documenting library interfaces, but it should be useful for any kind
of Haskell code.

Haddock lets you write documentation annotations next to the
definitions of functions and types in the source code, in a syntax
that is easy on the eye when writing the source code (no heavyweight
mark-up). The documentation generated by Haddock is fully hyperlinked
- click on a type name in a type signature to go straight to the
definition, and documentation, for that type.

Haddock understands Haskell's module system, so you can structure your
code however you like without worrying that internal structure will be
exposed in the generated documentation.  For example, it is common to
implement a library in several modules, but define the external API by
having a single module which re-exports parts of these implementation
modules.  Using Haddock, you can still write documentation annotations
next to the actual definitions of the functions and types in the
library, but the documentation annotations from the implementation
will be propagated to the external API when the documentation is
generated.  Abstract types and classes are handled correctly.  In
fact, even without any documentation annotations, Haddock can generate
useful documentation from your source code.

#### Documentation formats

Haddock can generate documentation in multiple formats; currently HTML
is implemented, and there is partial support for generating LaTeX and

#### Source code documentation

Full documentation can be found in the doc/ subdirectory, in DocBook

#### Contributing

Please create issues when you have any problems and pull requests if you have some code.

###### Hacking

To get started you'll need a latest GHC release installed. Below is an
example setup using cabal sandboxes.

  git clone
  cd haddock
  cabal sandbox init
  cabal sandbox add-source haddock-library
  cabal sandbox add-source haddock-api
  # adjust -j to the number of cores you want to use
  cabal install -j4 --dependencies-only --enable-tests
  cabal configure --enable-tests
  cabal build -j4
  # run the test suite
  cabal test

If you're a GHC developer and want to update Haddock to work with your
changes, you should be working on `ghc-head` branch instead of master.
See instructions at
for an example workflow.