From: simonmar Date: Mon, 10 Oct 2005 10:15:05 +0000 (+0000) Subject: [project @ 2005-10-10 10:15:05 by simonmar] X-Git-Tag: Initial_conversion_from_CVS_complete~183 X-Git-Url: http://git.megacz.com/?a=commitdiff_plain;h=1b85a989e426c5399cbdb0be6379f343ca36d6fb;p=ghc-hetmet.git [project @ 2005-10-10 10:15:05 by simonmar] identify "mode" as a class of flags, in addition to "static" and "dyanmic" --- diff --git a/ghc/docs/users_guide/using.xml b/ghc/docs/users_guide/using.xml index 22de98c..810d52a 100644 --- a/ghc/docs/users_guide/using.xml +++ b/ghc/docs/users_guide/using.xml @@ -96,21 +96,47 @@ module X where - Static vs. Dynamic options + Static, Dynamic, and Mode options staticoptions dynamicoptions + modeoptions + Each of GHC's command line options is classified as either - static or dynamic. - A static flag may only be specified on the command line, whereas a - dynamic flag may also be given in an OPTIONS_GHC - pragma in a source file or set from the GHCi command-line with - :set. - - As a rule of thumb, options which relate to filenames are - static, and the rest are dynamic. The flag reference tables (static or dynamic or + mode: + + + + Mode flags + + For example, or . + There may be only a single mode flag on the command line. The + available modes are listed in . + + + + Dynamic Flags + + Most non-mode flags fall into this category. A dynamic flag + may be used on the command line, in a + GHC_OPTIONS pragma in a source file, or set + using :set in GHCi. + + + + Static Flags + + A few flags are "static", which means they can only be used on + the command-line, and remain in force over the entire GHC/GHCi + run. + + + + + The flag reference tables () lists the status of each flag.