[haddock] #71: Derive portability information from pragmas

[haddock]

#71: Derive portability information from pragmas
------------------------------------------+---------------------------------
Reporter:  haddock at henning-thielemann.de  |        Owner:       
    Type:  enhancement                    |       Status:  new  
Priority:  minor                          |    Milestone:  2.6.0
 Version:                                 |   Resolution:       
Keywords:                                 |  
------------------------------------------+---------------------------------
Changes (by waern):

  * milestone:  2.5.0 => 2.6.0

Comment:

 It would be nice if the portability status of a module could be
 automatically inferred, yes. There is plan to implement something like
 this in Cabal. See:

   http://hackage.haskell.org/trac/hackage/ticket/370

 Cabal could easily pass this information via a command-line flag to
 Haddock. Now the question is: is it worth doing this in Haddock as well,
 for those cases when Cabal is not used to invoke Haddock? It might be, but
 we should not prioritise this issue much, IMHO.

 If we'd do it, we could look directly in the DynFlags (The GHC data type
 that represents compiler options) to determine exactly which extensions
 are used, so that we don't miss extensions turned on via the command line.

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