[[project @ 2001-03-28 10:34:15 by simonmar]
simonmar**20010328103415
Document the use of :set with command-line options a little better.
] {
hunk ./ghc/docs/users_guide/ghci.sgml 801
- options, which begin with ‘-’. Either type of option
- may be set using :set and unset using
- :unset.
+ options, which begin with ‘-’.
hunk ./ghc/docs/users_guide/ghci.sgml 803
- The available GHCi options are:
+
+ GHCi options
+ optionsGHCi
+
hunk ./ghc/docs/users_guide/ghci.sgml 808
-
-
- +r
- +r
- CAFsin GHCi
- Constant Applicative FormCAFs
-
- Normally, any evaluation of top-level expressions
- (otherwise known as CAFs or Constant Applicative Forms) in
- loaded modules is retained between evaluations. Turning on
- +r causes all evaluation of top-level
- expressions to be discarded after each evaluation (they are
- still retained during a single
- evaluation).
+ GHCi options may be set using :set and
+ unset using :unset.
+
+ The available GHCi options are:
+
+
+
+ +r
+ +r
+ CAFsin GHCi
+ Constant Applicative FormCAFs
+
+ Normally, any evaluation of top-level expressions
+ (otherwise known as CAFs or Constant Applicative Forms) in
+ loaded modules is retained between evaluations. Turning
+ on +r causes all evaluation of
+ top-level expressions to be discarded after each
+ evaluation (they are still retained
+ during a single evaluation).
hunk ./ghc/docs/users_guide/ghci.sgml 828
- This option may help if the evaluated top-level
- expressions are consuming large amounts of space, or if you
- need repeatable performance measurements.
-
-
+ This option may help if the evaluated top-level
+ expressions are consuming large amounts of space, or if
+ you need repeatable performance measurements.
+
+
+
+
+ +s
+ +s
+
+ Display some stats after evaluating each expression,
+ including the elapsed time and number of bytes allocated.
+ NOTE: the allocation figure is only accurate to the size
+ of the storage manager's allocation area, because it is
+ calculated at every GC. Hence, you might see values of
+ zero if no GC has occurred.
+
+
+
+
+ +t
+ +t
+
+ Display the type of each variable bound after a
+ statement is entered at the prompt. If the statement is a
+ single expression, then the only variable binding will be
+ for the variable
+ ‘it’.
+
+
+
+
+
+
+ Setting GHC command-line options in GHCi
+
+ Normal GHC command-line options may also be set using
+ :set. For example, to turn on
+ , you would say:
+
+
+Prelude> :set -fglasgow-exts
+
+
+ Any GHC command-line option that is designated as
+ dynamic (see the table in ), may be set using
+ :set. To unset an option, you can set the
+ reverse option:
+ dynamicoptions
hunk ./ghc/docs/users_guide/ghci.sgml 879
-
- +s
- +s
-
- Display some stats after evaluating each expression,
- including the elapsed time and number of bytes allocated.
- NOTE: the allocation figure is only accurate to the size of
- the storage manager's allocation area, because it is
- calculated at every GC. Hence, you might see values of zero
- if no GC has occurred.
-
-
+
+Prelude> :set -fno-glasgow-exts
+
hunk ./ghc/docs/users_guide/ghci.sgml 883
-
- +t
- +t
-
- Display the type of each variable bound after a
- statement is entered at the prompt. If the statement is a
- single expression, then the only variable binding will be
- for the variable ‘it’.
-
-
-
+ lists the reverse for each
+ option where applicable.
hunk ./ghc/docs/users_guide/ghci.sgml 886
- In addition, any normal GHC command-line option that is
- designated as dynamic (see the table in
- ), may be set using
- :set. Certain static options
- (, , and
- in particular) will also work, but may not take effect until the
- next reload.
- dynamicoptions
- staticoptions
+ Certain static options (,
+ , and in particular) will
+ also work, but may not take effect until the next reload.
+ staticoptions
+
}