[haddock] #83: Better parse error messages when parsing the contents of Haddock comments

[haddock]

#83: Better parse error messages when parsing the contents of Haddock comments
------------------------+---------------------------------------------------
Reporter:  waern        |        Owner:       
    Type:  enhancement  |       Status:  new  
Priority:  major        |    Milestone:  2.6.0
 Version:  2.4.1        |   Resolution:       
Keywords:               |  
------------------------+---------------------------------------------------
Comment (by waern):

 Unfortunately, it will always give you this extremely bad error message if
 you're using GHC >= 6.10.

 We have two regressions here:

   - We used to "show" the AST of the markup, but that was removed during
 the SoC project (I can't remember why, ATM).

   - With GHC < 6.10 we show the source location of the Haddock comment.
 When support for GHC 6.10 was added, an error handler was installed only
 around the typechecking phase, so we miss cases like this where (I think)
 an error is thrown during dependency chasing.

 I will try to fix this second regression as soon as possible (hopefully in
 time for 2.4.2). But we should also:

  - Pretty-print the Haddock comment
  - Give exact source location (from within the Haddock-comment).

 The two above enchancements should probably be done after we have moved
 the parser and lexer for Haddock comments from GHC back into Haddock (see
 #93).

-- 
Ticket URL: <http://trac.haskell.org/haddock/ticket/83#comment:3>
haddock <http://www.haskell.org/haddock>
Haddock, The Haskell Documentation Tool