From 8215287c8c8d19dff36cd20ef71d56341a769d50 Mon Sep 17 00:00:00 2001 From: Ian Lynagh Date: Mon, 16 Jul 2007 21:28:13 +0000 Subject: [PATCH] Doc tweaks --- docs/users_guide/separate_compilation.xml | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/users_guide/separate_compilation.xml b/docs/users_guide/separate_compilation.xml index 59723d7..58726e5 100644 --- a/docs/users_guide/separate_compilation.xml +++ b/docs/users_guide/separate_compilation.xml @@ -184,7 +184,7 @@ dots replaced by the directory separator ('/' or '\', depending on the system), and extension is a source extension (hs, lhs) - if we are in mode and GHCi, or + if we are in mode or GHCi, or hisuf otherwise. For example, suppose the search path contains directories @@ -220,7 +220,7 @@ This isn't the whole story: GHC also looks for modules in pre-compiled libraries, known as packages. See the section on - packages (), for details. + packages () for details. @@ -712,7 +712,7 @@ module A where To compile these three files, issue the following commands: - ghc -c A.hs-boot -- Poduces A.hi-boot, A.o-boot + ghc -c A.hs-boot -- Produces A.hi-boot, A.o-boot ghc -c B.hs -- Consumes A.hi-boot, produces B.hi, B.o ghc -c A.hs -- Consumes B.hi, produces A.hi, A.o ghc -o foo A.o B.o -- Linking the program @@ -778,7 +778,7 @@ When a hs-boot file A.hs-boot A module M that is {-# SOURCE #-}-imported in a program will usually also be ordinarily imported elsewhere. If not, ghc --make - automatically adds M to the set of moudles it tries to + automatically adds M to the set of modules it tries to compile and link, to ensure that M's implementation is included in the final program. @@ -824,7 +824,7 @@ can be given abstractly, by omitting the '=' sign and everything that follows. data R (x :: * -> *) y -You cannot use deriving on a data type declaration; write in +You cannot use deriving on a data type declaration; write an instance declaration instead. Class declarations is exactly as in Haskell, except that you may not put @@ -1184,7 +1184,7 @@ and GHC has no other reason for visiting the module. Example: class C a where ... Here, neither D nor T is declared in module Orphan. -We call such modules ``orphan modules'', +We call such modules “orphan modules”, defined thus: An orphan module @@ -1195,7 +1195,7 @@ defined thus: An instance declaration in a module M is an orphan instance if orphan instance none of the type constructors - or classes mentioned in the instance head (the part after the ``=>'') are declared + or classes mentioned in the instance head (the part after the “=>”) are declared in M. Only the instance head counts. In the example above, it is not good enough for C's declaration @@ -1219,8 +1219,8 @@ your best to have as few orphan modules as possible. You can identify an orphan module by looking in its interface file, M.hi, using the -. If there is a ``!'' on the first line, -GHC considers it an orphan module. +. If there is a “!” on the +first line, GHC considers it an orphan module. -- 1.7.10.4