[[project @ 2005-10-10 10:15:05 by simonmar] simonmar**20051010101505 identify "mode" as a class of flags, in addition to "static" and "dyanmic" ] { hunk ./ghc/docs/users_guide/using.xml 99 - Static vs. Dynamic options + Static, Dynamic, and Mode options hunk ./ghc/docs/users_guide/using.xml 104 + modeoptions + hunk ./ghc/docs/users_guide/using.xml 108 - 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. + static or dynamic or + mode: hunk ./ghc/docs/users_guide/using.xml 111 - As a rule of thumb, options which relate to filenames are - static, and the rest are dynamic. The flag reference tables ( + + 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 (