The haddock package

[Tags:bsd3, program, test]

Haddock is a documentation-generation tool for Haskell libraries

[Skip to Readme]


Versions 0.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, 2.17.2
Change log CHANGES
Dependencies array, base, containers, directory, filepath, ghc (==6.8.2 || ==6.8.3), ghc-paths (<=, haskell98, pretty [details]
License BSD3
Copyright (c) Simon Marlow, David Waern
Author Simon Marlow, David Waern
Maintainer David Waern <>
Stability experimental
Category Development
Home page
Uploaded Fri Jul 25 21:20:39 UTC 2008 by DavidWaern
Distributions Debian:2.13.1, FreeBSD:2.16.1, NixOS:2.17.2
Downloads 46135 total (372 in the last 30 days)
0 []
Status Docs uploaded by user
Build status unknown [no reports yet]




Maintainer's Corner

For package maintainers and hackage trustees

Readme for haddock

Readme for haddock-2.2.0

Haddock, a Haskell Documentation Tool

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.

Like other systems ([1],[2]), 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.

Haddock can generate documentation in multiple formats; currently HTML
is implemented, and there is partial support for generating DocBook.
The generated HTML uses stylesheets, so you need a fairly up-to-date
browser to view it properly (Mozilla, Konqueror, Opera, and IE 6
should all be ok).

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

Please send questions and suggestions to:

David Waern <> or
Simon Marlow <>

[1] IDoc - A No Frills Haskell Interface Documentation System

[2] HDoc