diff options
author | simonmar <unknown> | 2005-01-18 10:02:48 +0000 |
---|---|---|
committer | simonmar <unknown> | 2005-01-18 10:02:48 +0000 |
commit | 60824c6ef91bc454d449bf29d09ac5badf49b5f8 (patch) | |
tree | 663d5eb5723fc8e22c5fc66504575501d79d30c9 | |
parent | f1c4b8922e32871a26b8074ef12392b9b8c8e662 (diff) |
[haddock @ 2005-01-18 10:02:48 by simonmar]
Add a TODO
-rw-r--r-- | TODO | 13 |
1 files changed, 13 insertions, 0 deletions
@@ -1,6 +1,16 @@ ----------------------------------------------------------------------------- -- bugs +* I've been thinking of a solution along these lines: Haddock + processes the modules in two phases. The first phase resolves all the + names and determines the "definitive" documentation for each entity. + The second phase makes all the links point to the definitive + documentation, with certain exceptions: if the entity is also + documented in the local module, then point there instead. Perhaps + there are other exceptions. We might need a way to indicate + "definitive", or maybe just the module(s) furthest up the dependency + tree would do. + * The lexer should handle "...." in doc strings, only recognising it if the contents looks like a module name. @@ -51,6 +61,9 @@ * Command-line flag to give the effect of --#ignore-exports on all modules (request by Chris Ryder, for generating implementation docs.) +* Command-line flags to hide modules (easier for Cabal to use than requiring + #hide directives in the source). + * Parse and remember {-# SOURCE #-} imports, possibly do something sensible with them? |