From: simonpj <unknown>
Date: Mon, 12 Jan 2004 10:02:51 +0000 (+0000)
Subject: [project @ 2004-01-12 10:02:51 by simonpj]
X-Git-Tag: Approx_11550_changesets_converted~132
X-Git-Url: http://git.megacz.com/?p=ghc-hetmet.git;a=commitdiff_plain;h=9a9feb62db17daf7f2566395f719c2aecec5feb0

[project @ 2004-01-12 10:02:51 by simonpj]
Elaborate depreceated-pragma docs
---

diff --git a/ghc/docs/users_guide/glasgow_exts.sgml b/ghc/docs/users_guide/glasgow_exts.sgml
index db91ac0..025a923 100644
--- a/ghc/docs/users_guide/glasgow_exts.sgml
+++ b/ghc/docs/users_guide/glasgow_exts.sgml
@@ -3943,7 +3943,7 @@ Assertion failures can be caught, see the documentation for the
 
       <para>The DEPRECATED pragma lets you specify that a particular
       function, class, or type, is deprecated.  There are two
-      forms.</para>
+      forms.
 
       <itemizedlist>
 	<listitem>
@@ -3968,7 +3968,15 @@ Assertion failures can be caught, see the documentation for the
           message.</para>
 	</listitem>
       </itemizedlist>
-
+      Any use of the deprecated item, or of anything from a deprecated
+      module, will be flagged with an appropriate message.  However,
+      deprecations are not reported for
+      (a) uses of a deprecated function within its defining module, and
+      (b) uses of a deprecated function in an export list.
+      The latter reduces spurious complaints within a library
+      in which one module gathers together and re-exports 
+      the exports of several others.
+      </para>
       <para>You can suppress the warnings with the flag
       <option>-fno-warn-deprecations</option>.</para>
     </sect2>