X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=docs%2Fusers_guide%2Fseparate_compilation.xml;h=01748ae9261d66c1ca023a2287210b8b77042b25;hb=2fa48f4ea462a6e7f0bb22a8c292ee4efcec81e0;hp=bc3afcab6342807034f052804756e9287cb39ea5;hpb=e42d6cb48df657053029aff833de1151cf7349bf;p=ghc-hetmet.git diff --git a/docs/users_guide/separate_compilation.xml b/docs/users_guide/separate_compilation.xml index bc3afca..01748ae 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: -GHC will warn you if you are creating an orphan module, if you add `-fwarn-orphan-modules`. +If you use the flag , GHC will warn you +if you are creating an orphan module. +Like any warning, you can switch the warning off with , +and +will make the compilation fail if the warning is issued. + + You can identify an orphan module by looking in its interface file, M.hi, using the mode. If there is a [orphan module] on the