| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Pay attention to import specs when building the the import env, as
well as the orig env. This may fix some wrong links in documentation
when import specs are being used.
|
| |
|
|
| |
Make it compile with GHC >= 6.01
|
| |
|
|
| |
Markup fix
|
| |
|
|
| |
Update for 0.5
|
| |
|
|
| |
Update to avoid using hslibs with GHC >= 5.04
|
| |
|
|
|
| |
* Updated to version 0.5
* Automagically generate configure if it is not there
|
| |
|
|
| |
Update to version 0.5
|
| |
|
|
|
|
| |
When a module A exports another module's contents via 'module B', then
modules which import entities from B re-exported by A should link to
B.foo rather than A.foo. See examples/Bug2.hs.
|
| |
|
|
|
| |
Differentiate links to types/classes from links to
variables/constructors with a prefix ("t:" and "v:" respectively).
|
| |
|
|
| |
layout tweak.
|
| |
|
|
| |
Update
|
| |
|
|
| |
Add documentation for anchors.
|
| |
|
|
| |
Add tests for a couple of bugs.
|
| |
|
|
|
|
| |
Two small fixes to make the output valid HTML 4.01 (transitional).
Thanks to Malcolm Wallace for pointing out the problems.
|
| |
|
|
| |
oops, drop test defn from prev commit
|
| |
|
|
| |
cygpath: for now, steer clear of --mixed
|
| |
|
|
| |
Only omit the module contents when there are no section headings at all.
|
| |
|
|
|
| |
Don't turn a single DocCodeBlock into a DocMonospaced, because that
tends to remove the line breaks in the code.
|
| |
|
|
| |
Add some more code-block tests.
|
| |
|
|
|
| |
Catch another case of a paragraph containing just a DocMonospaced that
should turn into a DocCodeBlock.
|
| |
|
|
|
|
|
|
| |
When installing on Windows, run cygpath over $(HADDOCKLIB) so that
haddock (a mingw program, built by GHC) can understand it.
You still need to be in a cygwin environment to run Haddock, because
of the shell script wrapper.
|
| |
|
|
|
|
| |
Some updates, including moving the derived instance item down to the
bottom of the list now that Ross has contributed some code that does
the job for common cases.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
An 80% solution to generating derived instances. A complete solution
would duplicate the instance inference logic, but if a type variable
occurs as a constructor argument, then we can just propagate the derived
class to the variable. But we know nothing of the constraints on any
type variables that occur elsewhere. For example, the declarations
data Either a b = Left a | Right b deriving (Eq, Ord)
data Ptr a = Ptr Addr# deriving (Eq, Ord)
newtype IORef a = IORef (STRef RealWorld a) deriving Eq
yield the instances
(Eq a, Eq b) => Eq (Either a b)
(Ord a, Ord b) => Ord (Either a b)
Eq (Ptr a)
Ord (Ptr a)
(??? a) => Eq (IORef a)
The last example shows the limits of this local analysis.
Note that a type variable may be in both categories: then we know a
constraint, but there may be more, or a stronger constraint, e.g.
data Tree a = Node a [Tree a] deriving Eq
yields
(Eq a, ??? a) => Eq (Tree a)
|
| |
|
|
| |
Escape fragments. This fixes e.g. links to operators.
|
| |
|
|
|
| |
Don't append a fragment to non-defining index entries, only documents
with a defining occurrence have a name anchor.
|
| |
|
|
|
| |
Fixed some broken/redirected/canonicalized links found by a very picky
link checker.
|
| |
|
|
|
|
|
|
| |
Don't convert a "newtype" to a single-constructor "data" for
non-abstractly exported types, they are quite different regarding
strictness/pattern matching. Now a "data" without any constructors is
only emitted for an abstractly exported type, regardless if it is
actually a "newtype" or a "data".
|
| |
|
|
|
| |
* Add varsyms and consyms to index
* Exclude empty entries from index
|
| |
|
|
| |
Adjust for the new exception libraries (as well as the old ones).
|
| |
|
|
| |
Small bugfix in the --read-interface option parsing from Brett Letner.
|
| |
|
|
| |
Fix cut-n-pasto
|
| |
|
|
| |
update
|
| |
|
|
|
|
|
| |
Remove <P>..</P> from around list items, to reduce excess whitespace
between the items of bulleted and ordered lists.
(Suggestion from Daan Leijen).
|
| |
|
|
|
|
|
| |
The <TT> and <PRE> environments seem to use a font that is a little
too small in IE. Compensate.
(suggestion from Daan Leijen).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Patch to allow simple hyperlinking to an arbitrary location in another
module's documentation, from Volker Stolz.
Now in a doc comment:
#foo#
creates
<a name="foo"></a>
And you can use the form "M\#foo" to hyperlink to the label 'foo' in
module 'M'. Note that the backslash is necessary for now.
|
| |
|
|
| |
Patches to quieten ghc -Wall, from those nice folks at Galois.
|
| |
|
|
| |
Remove ^Ms
|
| |
|
|
| |
Add a version banner when invoked with -v
|
| |
|
|
| |
Another item for the TODO list
|
| |
|
|
| |
Fix the %changelog (rpm complained that it wasn't in the right order)
|
| |
|
|
| |
Updates for version 0.4
|
| |
|
|
| |
more tests
|
| |
|
|
|
|
|
| |
- update the acknowledgements
- remove the paragraph that described how to use explicit layout with
doc comments; it isn't relevant any more.
|
| |
|
|
| |
A new TODO list item
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Relax the restrictions which require doc comments to be followed by
semi colons - in some cases this isn't necessary. Now you can write
module M where {
-- | some doc
class C where {}
}
without needing to put a semicolon before the class declaration.
|
| |
|
|
| |
Allow special id's ([], (), etc.) to be used in an import declarations.
|
| |
|
|
| |
Allow special id's ([], (), etc.) to be used in an import declaration.
|
| |
|
|
|
|
|
|
| |
Allow multiple sections/subsections before and after a comma in the
export list.
Also at the same time I made the syntax a little stricter (multiple
commas now aren't allowed between export specs).
|
| |
|
|
| |
Mention alternative commenting styles.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Be a bit more liberal in the kind of commenting styles we allow, as
suggested by Malcolm Wallace. Mostly this consists of allowing doc
comments either side of a separator token.
In an export list, a section heading is now allowed before the comma,
as well as after it. eg.
module M where (
T(..)
-- * a section heading
, f
-- * another section heading
, g
)
In record fields, doc comments are allowed anywhere (previously a
doc-next was allowed only after the comma, and a doc-before was
allowed only before the comma). eg.
data R = C {
-- | describes 'f'
f :: Int
-- | describes 'g'
, g :: Int
}
|
