summaryrefslogtreecommitdiff
path: root/docs/users_guide/separate_compilation.xml
diff options
context:
space:
mode:
authorsimonpj@microsoft.com <unknown>2008-08-14 15:26:48 +0000
committersimonpj@microsoft.com <unknown>2008-08-14 15:26:48 +0000
commit2f979bf83bad9b012efa225c38cfcd7ea91b2b29 (patch)
tree6c6ae212863b3d560f56e637d1c360a3cd78e482 /docs/users_guide/separate_compilation.xml
parentc9e8286bf57931bd9daa0135326a7857c2351d03 (diff)
downloadhaskell-2f979bf83bad9b012efa225c38cfcd7ea91b2b29.tar.gz
Improve -fwarn-orphans documentation (thanks to Tim)
Diffstat (limited to 'docs/users_guide/separate_compilation.xml')
-rw-r--r--docs/users_guide/separate_compilation.xml8
1 files changed, 7 insertions, 1 deletions
diff --git a/docs/users_guide/separate_compilation.xml b/docs/users_guide/separate_compilation.xml
index bc3afcab63..01748ae926 100644
--- a/docs/users_guide/separate_compilation.xml
+++ b/docs/users_guide/separate_compilation.xml
@@ -1247,7 +1247,13 @@ These considerations lead to the following definition of an orphan module:
-<para>GHC will warn you if you are creating an orphan module, if you add `-fwarn-orphan-modules`.
+<para>If you use the flag <option>-fwarn-orphans</option>, GHC will warn you
+if you are creating an orphan module.
+Like any warning, you can switch the warning off with <option>-fno-warn-orphans</option>,
+and <option>-Werror</option>
+will make the compilation fail if the warning is issued.
+</para>
+<para>
You can identify an orphan module by looking in its interface
file, <filename>M.hi</filename>, using the
<link linkend="modes"><option>--show-iface</option> mode</link>. If there is a <literal>[orphan module]</literal> on the