aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorsimonmar <unknown>2002-07-23 08:40:56 +0000
committersimonmar <unknown>2002-07-23 08:40:56 +0000
commite5d775864dfa52d588aee8f0ce41ef66181e9e05 (patch)
treedcddcf2183f7a83c854003bf47bc4c89b9ab8535 /doc
parente9301e1432e921e0a0dcae02c3f193b537b17f06 (diff)
[haddock @ 2002-07-23 08:40:56 by simonmar]
- update the acknowledgements - remove the paragraph that described how to use explicit layout with doc comments; it isn't relevant any more.
Diffstat (limited to 'doc')
-rw-r--r--doc/haddock.sgml17
1 files changed, 4 insertions, 13 deletions
diff --git a/doc/haddock.sgml b/doc/haddock.sgml
index 3d1a0304..58784f56 100644
--- a/doc/haddock.sgml
+++ b/doc/haddock.sgml
@@ -187,9 +187,10 @@
<para>Thanks to the following people for useful feedback,
discussion, patches, packaging, and moral support: Simon Peyton
Jones, Mark Shields, Manuel Chakravarty, Ross Patterson, Brett
- Letner, Sven Panne, Hal Daume, George Russell, Oliver Braun, the
- members of <email>haskelldoc@haskell.org</email>, and everyone
- who contributed to the many libraries that Haddock makes use
+ Letner, Sven Panne, Hal Daume, George Russell, Oliver Braun,
+ Ashley Yakeley, Malcolm Wallace, Krasimir Angelov, the members
+ of <email>haskelldoc@haskell.org</email>, and everyone who
+ contributed to the many libraries that Haddock makes use
of.</para>
</section>
@@ -568,16 +569,6 @@ class C a where
-- | This is the documentation for the 'g' method
g :: Int -> a
</programlisting>
-
- <para>Note that in Haddock documentation annotations are
- first-class syntactic objects that are subject to the same
- layout rules as other syntactic objects; thus in the example
- class declaration above the documentation annotations must
- begin in the same column as the method signatures. If you use
- explicit layout, then don't forget the semi-colon after each
- documentation comment (but don't put the semi-colon on the
- same line as the documentation comment, because it will be
- interpreted as part of the documentation!).</para>
</section>
<section>