X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=docs%2Fusers_guide%2Fghci.xml;h=c0167bfe09d924eb726d3183a3afe14b954854b2;hb=d4050431de1adddedb240e497f77f89301f77070;hp=d3efd2a7f43494bb5987e981987f3cab1139a7f6;hpb=84d072eaeeeb3decfc39a96c033b9fa2ec3baec5;p=ghc-hetmet.git
diff --git a/docs/users_guide/ghci.xml b/docs/users_guide/ghci.xml
index d3efd2a..c0167bf 100644
--- a/docs/users_guide/ghci.xml
+++ b/docs/users_guide/ghci.xml
@@ -564,7 +564,7 @@ Prelude IO>
Hint: GHCi will tab-complete names that are in scope; for
example, if you run GHCi and type J<tab>
- then GHCi will expand it to Just .
+ then GHCi will expand it to “Just ”.
@@ -715,7 +715,7 @@ it <- e
At the GHCi prompt, or with GHC if the
- -fextended-default-rules flag is given,
+ -XExtendedDefaultRules flag is given,
the following additional differences apply:
@@ -764,8 +764,8 @@ def = toEnum 0
instance that returns IO a.
However, it is only able to return
undefined
- (the reason for the instance having this type is to not require
- extensions to the class system), so if the type defaults to
+ (the reason for the instance having this type is so that printf
+ doesn't require extensions to the class system), so if the type defaults to
Integer then ghci gives an error when running a
printf.
@@ -788,7 +788,7 @@ def = toEnum 0
The debugger provides the following:
- The abilty to set a breakpoint on a
+ The ability to set a breakpoint on a
function definition or expression in the program. When the function
is called, or the expression evaluated, GHCi suspends
execution and returns to the prompt, where you can inspect the
@@ -1017,7 +1017,7 @@ right :: [a]
The execution continued at the point it previously stopped, and has
now stopped at the breakpoint for a second time.
-
+
Setting breakpoints
Breakpoints can be set in various ways. Perhaps the easiest way to
@@ -1080,7 +1080,7 @@ right :: [a]
Listing and deleting breakpoints
The list of breakpoints currently enabled can be displayed using
- :show breaks:
+ :show breaks:
*Main> :show breaks
[0] Main qsort.hs:1:11-12
@@ -1488,7 +1488,7 @@ Just 20
Implicit parameters (see ) are only available
- at the scope of a breakpoint if there is a explicit type signature.
+ at the scope of a breakpoint if there is an explicit type signature.
@@ -1516,9 +1516,7 @@ $ ghci Main.hs
Most of the command-line options accepted by GHC (see ) also make sense in interactive mode. The ones
- that don't make sense are mostly obvious; for example, GHCi
- doesn't generate interface files, so options related to interface
- file generation won't have any effect.
+ that don't make sense are mostly obvious.
Packages
@@ -1534,12 +1532,7 @@ $ ghci Main.hs
$ ghci -package readline
- ___ ___ _
- / _ \ /\ /\/ __(_)
- / /_\// /_/ / / | | GHC Interactive, version 6.6, for Haskell 98.
-/ /_\\/ __ / /___| | http://www.haskell.org/ghc/
-\____/\/ /_/\____/|_| Type :? for help.
-
+GHCi, version 6.8.1: http://www.haskell.org/ghc/ :? for help
Loading package base ... linking ... done.
Loading package readline-1.0 ... linking ... done.
Prelude>
@@ -1711,16 +1704,6 @@ $ ghci -lm
- :continue
- :continue
-
- Continue the current evaluation, when stopped at a
- breakpoint.
-
-
-
-
-
:cmd expr
:cmd
@@ -1735,6 +1718,16 @@ $ ghci -lm
+ :continue
+ :continue
+
+ Continue the current evaluation, when stopped at a
+ breakpoint.
+
+
+
+
+
:ctags filename
:etags filename
:etags
@@ -1744,7 +1737,8 @@ $ ghci -lm
Generates a “tags” file for Vi-style editors
- (:ctags) or Emacs-style editors (etags). If
+ (:ctags) or
+ Emacs-style editors (:etags). If
no filename is specified, the defaulit tags or
TAGS is
used, respectively. Tags for all the functions, constructors and
@@ -1852,6 +1846,15 @@ Prelude> :. cmds.ghci
+ :etags
+
+
+ See :ctags.
+
+
+
+
+
:force identifier ...
:force
@@ -1988,7 +1991,7 @@ Prelude> :. cmds.ghci
However, we cannot simply pass the arguments to the
main function while we are testing in ghci,
as the main function doesn't take its
- directly.
+ arguments directly.
@@ -2033,7 +2036,7 @@ Prelude> :main foo bar
Prints a value without forcing its evaluation.
:print may be used on values whose types are
- unkonwn or partially known, which might be the case for local
+ unknown or partially known, which might be the case for local
variables with polymorphic types at a breakpoint. While inspecting
the runtime value, :print attempts to
reconstruct the type of the value, and will elaborate the type in
@@ -2053,7 +2056,7 @@ Prelude> :main foo bar
:quit
- Quits GHCi. You can also quit by typing a control-D
+ Quits GHCi. You can also quit by typing control-D
at the prompt.
@@ -2198,7 +2201,7 @@ Prelude> :main foo bar
:show modules
- Show the list of modules currently load.
+ Show the list of modules currently loaded.
@@ -2309,7 +2312,7 @@ Prelude> :main foo bar
The :set command sets two types of
options: GHCi options, which begin with
- ‘+” and “command-line”
+ ‘+’, and “command-line”
options, which begin with ‘-’.
NOTE: at the moment, the :set command
@@ -2421,9 +2424,10 @@ Prelude> :set -fno-glasgow-exts
startupfiles, GHCi
- When it starts, GHCi always reads and executes commands from
- $HOME/.ghci, followed by
- ./.ghci.
+ When it starts, unless the -ignore-dot-ghci
+ flag is given, GHCi reads and executes commands from
+ ./.ghci, followed by
+ $HOME/.ghci.
The .ghci in your home directory is
most useful for turning on favourite options (eg. :set
@@ -2432,7 +2436,7 @@ Prelude> :set -fno-glasgow-exts
project is a useful way to set certain project-wide options so you
don't have to type them everytime you start GHCi: eg. if your
project uses GHC extensions and CPP, and has source files in three
- subdirectories A B and C, you might put the following lines in
+ subdirectories A, B and C, you might put the following lines in
.ghci:
@@ -2580,7 +2584,7 @@ Prelude> :set -fno-glasgow-exts
I can't use Control-C to interrupt computations in
GHCi on Windows.
- See
+ See .