X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=ghc%2Fdocs%2Fusers_guide%2Fusing.xml;fp=ghc%2Fdocs%2Fusers_guide%2Fusing.xml;h=810d52a9a67e834b0283e769f53cdc00e78d6a7d;hb=1b85a989e426c5399cbdb0be6379f343ca36d6fb;hp=22de98c943998ddbd5e0629633a8c2aeff71b1c4;hpb=4b0b74b603640af797df679ba7a664779bd55842;p=ghc-hetmet.git 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.