
-------------------------------------------- -- Haddock 2.10.0 -------------------------------------------- Version 2.10.0, which was released with GHC 7.4.1, is now uploaded on Hackage. Here are the release notes: -------------------------------------------- -- Changes in 2.10.0 -------------------------------------------- * Require GHC >= 7.4 * Safe Haskell indications on module pages * Type declarations on identifiers no longer necessary * Add flag --interface-version * Warn when comment refers to in-scope identifier without documentation * Bug fix: links to out-of-scope things (#78) * Bug fix: module references to other packages work again -------------------------------------------- -- Links -------------------------------------------- Hackage page: http://hackage.haskell.org/package/haddock-2.10.0 Bugtracker and wiki: http://trac.haskell.org/haddock Mailing list: haddock@projects.haskell.org Code repository: http://darcs.haskell.org/haddock.git -------------------------------------------- -- Contributors -------------------------------------------- The following people contributed patches to this release: Ian Lynagh Jose Pedro Magalhaes Simon Peyton-Jones Ryan Newton David Terei David Waern Also thanks to Simon Hengel for spotting a serious bug before the release. -------------------------------------------- -- Get Involved -------------------------------------------- We would be very happy to get more contributors. To get involved, start by grabbing the code: http://darcs.haskell.org/haddock.git Then take a look at the bug and feature tracker for things to work on: http://trac.haskell.org/haddock

-------------------------------------------- -- Haddock 2.10.0 --------------------------------------------
Version 2.10.0, which was released with GHC 7.4.1, is now uploaded on Hackage.
Nice, thank you! It seems to fail to generate buildwrapper documentation. The minimal example: -- Base.hs: module Base where -- | component in cabal file data CabalComponent = CCLibrary -- ^ library { cc_buildable :: Bool -- ^ is the library buildable } $ haddock Base.hs Haddock coverage: Base.hs:7:9: parse error on input `{' -- Sergei

2012/3/3 Sergei Trofimovich
It seems to fail to generate buildwrapper documentation. The minimal example:
-- Base.hs: module Base where
-- | component in cabal file data CabalComponent = CCLibrary -- ^ library { cc_buildable :: Bool -- ^ is the library buildable }
You can't stick a doc comment between a constructor and its arguments. Try putting the comment after the record closing bracket instead (or tell the author of the code). David

On Sat, 3 Mar 2012 21:12:26 +0100
David Waern
2012/3/3 Sergei Trofimovich
: It seems to fail to generate buildwrapper documentation. The minimal example:
-- Base.hs: module Base where
-- | component in cabal file data CabalComponent = CCLibrary -- ^ library { cc_buildable :: Bool -- ^ is the library buildable }
You can't stick a doc comment between a constructor and its arguments. Try putting the comment after the record closing bracket instead (or tell the author of the code).
Thanks! Fixed upstream. Let me bother you with another example (looks like a regression this time). Example comes from probability-0.2.3.1 package (selfcontained example attached). Haddock seems to have stopped liking utf-8 special chars in comments like: n² × n² n·(n+1)/2 $ haddock-2.10.0 -v3 Kruskal.hs Creating interfaces... Haddock coverage: Checking module Kruskal... Creating interface... haddock: internal error: lexical error $ haddock-2.9.2 -v3 Kruskal.hs haddock -v3 Kruskal.hs Creating interfaces... Checking module Kruskal... Creating interface... haddock coverage for Kruskal.hs: 0/1 0% Attaching instances... Building cross-linking environment... Renaming interfaces... -- Sergei

2012/3/4 Sergei Trofimovich
Thanks! Fixed upstream. Let me bother you with another example (looks like a regression this time). Example comes from probability-0.2.3.1 package (selfcontained example attached).
Haddock seems to have stopped liking utf-8 special chars in comments like: n² × n² n·(n+1)/2
Thanks for the report. I think unicode worked mostly by accident before and a recent change to support Alex 3 might unfortunately have turned that off. We're working on full support for unicode and I think we'll be able to get that into the next release. Sorry for the regression! David
participants (2)
-
David Waern
-
Sergei Trofimovich