From 194e778d542875df662986c48a0e8832be880247 Mon Sep 17 00:00:00 2001 From: Ian Lynagh Date: Mon, 16 Jul 2007 18:35:40 +0000 Subject: [PATCH] Doc tweaks --- docs/users_guide/using.xml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/users_guide/using.xml b/docs/users_guide/using.xml index a44ddfc..eb032df 100644 --- a/docs/users_guide/using.xml +++ b/docs/users_guide/using.xml @@ -379,9 +379,9 @@ module X where interfaces, and include files (usually something like /usr/local/lib/ghc-5.04 on Unix). This is the value of - $libdirlibdir - in the package configuration file (see ). + $libdirlibdir + in the package configuration file + (see ). @@ -394,7 +394,7 @@ module X where When given the option, GHC will build a multi-module Haskell program by following - dependencies from a single root module (usually + dependencies from one or more root modules (usually just Main). For example, if your Main module is in a file called Main.hs, you could compile and link the @@ -408,7 +408,7 @@ ghc ––make Main.hs names or module names; GHC will figure out all the modules in the program by following the imports from these initial modules. It will then attempt to compile each module which is out of - date, and finally if there is a Main module, + date, and finally, if there is a Main module, the program will also be linked into an executable. The main advantages to using ghc @@ -503,7 +503,7 @@ olleh The first phase to run is determined by each input-file suffix, and the last phase is determined by a flag. If no - relevant flag is present, then go all the way through linking. + relevant flag is present, then go all the way through to linking. This table summarises: -- 1.7.10.4