:stepover ---> :steplocal, :stepmodule
[ghc.git] / docs / users_guide / ghci.xml
1 <?xml version="1.0" encoding="iso-8859-1"?>
2 <chapter id="ghci">
3 <title>Using GHCi</title>
4 <indexterm><primary>GHCi</primary></indexterm>
5 <indexterm><primary>interpreter</primary><see>GHCi</see></indexterm>
6 <indexterm><primary>interactive</primary><see>GHCi</see></indexterm>
7
8 <para>GHCi<footnote>
9 <para>The &lsquo;i&rsquo; stands for &ldquo;Interactive&rdquo;</para>
10 </footnote>
11 is GHC's interactive environment, in which Haskell expressions can
12 be interactively evaluated and programs can be interpreted. If
13 you're familiar with <ulink url="http://www.haskell.org/hugs/">Hugs</ulink><indexterm><primary>Hugs</primary>
14 </indexterm>, then you'll be right at home with GHCi. However, GHCi
15 also has support for interactively loading compiled code, as well as
16 supporting all<footnote><para>except <literal>foreign export</literal>, at the moment</para>
17 </footnote> the language extensions that GHC provides.
18 <indexterm><primary>FFI</primary><secondary>GHCi support</secondary></indexterm>
19 <indexterm><primary>Foreign Function
20 Interface</primary><secondary>GHCi support</secondary></indexterm>.
21 GHCi also includes an interactive debugger (see <xref linkend="ghci-debugger"/>).</para>
22
23 <sect1 id="ghci-introduction">
24 <title>Introduction to GHCi</title>
25
26 <para>Let's start with an example GHCi session. You can fire up
27 GHCi with the command <literal>ghci</literal>:</para>
28
29 <screen>
30 $ ghci
31 GHCi, version 6.8.1: http://www.haskell.org/ghc/ :? for help
32 Loading package base ... linking ... done.
33 Prelude>
34 </screen>
35
36 <para>There may be a short pause while GHCi loads the prelude and
37 standard libraries, after which the prompt is shown. As the banner
38 says, you can type <literal>:?</literal> to see the list of commands
39 available, and a half line description of each of them.</para>
40
41 <para>We'll explain most of these commands as we go along. For
42 Hugs users: many things work the same as in Hugs, so you should be
43 able to get going straight away.</para>
44
45 <para>Haskell expressions can be typed at the prompt:</para>
46 <indexterm><primary>prompt</primary><secondary>GHCi</secondary>
47 </indexterm>
48
49 <screen>
50 Prelude> 1+2
51 3
52 Prelude> let x = 42 in x / 9
53 4.666666666666667
54 Prelude>
55 </screen>
56
57 <para>GHCi interprets the whole line as an expression to evaluate.
58 The expression may not span several lines - as soon as you press
59 enter, GHCi will attempt to evaluate it.</para>
60 </sect1>
61
62 <sect1 id="loading-source-files">
63 <title>Loading source files</title>
64
65 <para>Suppose we have the following Haskell source code, which we
66 place in a file <filename>Main.hs</filename>:</para>
67
68 <programlisting>
69 main = print (fac 20)
70
71 fac 0 = 1
72 fac n = n * fac (n-1)
73 </programlisting>
74
75 <para>You can save <filename>Main.hs</filename> anywhere you like,
76 but if you save it somewhere other than the current
77 directory<footnote><para>If you started up GHCi from the command
78 line then GHCi's current directory is the same as the current
79 directory of the shell from which it was started. If you started
80 GHCi from the &ldquo;Start&rdquo; menu in Windows, then the
81 current directory is probably something like
82 <filename>C:\Documents and Settings\<replaceable>user
83 name</replaceable></filename>.</para> </footnote> then we will
84 need to change to the right directory in GHCi:</para>
85
86 <screen>
87 Prelude> :cd <replaceable>dir</replaceable>
88 </screen>
89
90 <para>where <replaceable>dir</replaceable> is the directory (or
91 folder) in which you saved <filename>Main.hs</filename>.</para>
92
93 <para>To load a Haskell source file into GHCi, use the
94 <literal>:load</literal> command:</para>
95 <indexterm><primary><literal>:load</literal></primary></indexterm>
96
97 <screen>
98 Prelude> :load Main
99 Compiling Main ( Main.hs, interpreted )
100 Ok, modules loaded: Main.
101 *Main>
102 </screen>
103
104 <para>GHCi has loaded the <literal>Main</literal> module, and the
105 prompt has changed to &ldquo;<literal>*Main></literal>&rdquo; to
106 indicate that the current context for expressions typed at the
107 prompt is the <literal>Main</literal> module we just loaded (we'll
108 explain what the <literal>*</literal> means later in <xref
109 linkend="ghci-scope"/>). So we can now type expressions involving
110 the functions from <filename>Main.hs</filename>:</para>
111
112 <screen>
113 *Main> fac 17
114 355687428096000
115 </screen>
116
117 <para>Loading a multi-module program is just as straightforward;
118 just give the name of the &ldquo;topmost&rdquo; module to the
119 <literal>:load</literal> command (hint: <literal>:load</literal>
120 can be abbreviated to <literal>:l</literal>). The topmost module
121 will normally be <literal>Main</literal>, but it doesn't have to
122 be. GHCi will discover which modules are required, directly or
123 indirectly, by the topmost module, and load them all in dependency
124 order.</para>
125
126 <sect2 id="ghci-modules-filenames">
127 <title>Modules vs. filenames</title>
128 <indexterm><primary>modules</primary><secondary>and filenames</secondary></indexterm>
129 <indexterm><primary>filenames</primary><secondary>of modules</secondary></indexterm>
130
131 <para>Question: How does GHC find the filename which contains
132 module <replaceable>M</replaceable>? Answer: it looks for the
133 file <literal><replaceable>M</replaceable>.hs</literal>, or
134 <literal><replaceable>M</replaceable>.lhs</literal>. This means
135 that for most modules, the module name must match the filename.
136 If it doesn't, GHCi won't be able to find it.</para>
137
138 <para>There is one exception to this general rule: when you load
139 a program with <literal>:load</literal>, or specify it when you
140 invoke <literal>ghci</literal>, you can give a filename rather
141 than a module name. This filename is loaded if it exists, and
142 it may contain any module you like. This is particularly
143 convenient if you have several <literal>Main</literal> modules
144 in the same directory and you can't call them all
145 <filename>Main.hs</filename>.</para>
146
147 <para>The search path for finding source files is specified with
148 the <option>-i</option> option on the GHCi command line, like
149 so:</para>
150 <screen>ghci -i<replaceable>dir<subscript>1</subscript></replaceable>:...:<replaceable>dir<subscript>n</subscript></replaceable></screen>
151
152 <para>or it can be set using the <literal>:set</literal> command
153 from within GHCi (see <xref
154 linkend="ghci-cmd-line-options"/>)<footnote><para>Note that in
155 GHCi, and <option>&ndash;&ndash;make</option> mode, the <option>-i</option>
156 option is used to specify the search path for
157 <emphasis>source</emphasis> files, whereas in standard
158 batch-compilation mode the <option>-i</option> option is used to
159 specify the search path for interface files, see <xref
160 linkend="search-path"/>.</para> </footnote></para>
161
162 <para>One consequence of the way that GHCi follows dependencies
163 to find modules to load is that every module must have a source
164 file. The only exception to the rule is modules that come from
165 a package, including the <literal>Prelude</literal> and standard
166 libraries such as <literal>IO</literal> and
167 <literal>Complex</literal>. If you attempt to load a module for
168 which GHCi can't find a source file, even if there are object
169 and interface files for the module, you'll get an error
170 message.</para>
171 </sect2>
172
173 <sect2>
174 <title>Making changes and recompilation</title>
175 <indexterm><primary><literal>:reload</literal></primary></indexterm>
176
177 <para>If you make some changes to the source code and want GHCi
178 to recompile the program, give the <literal>:reload</literal>
179 command. The program will be recompiled as necessary, with GHCi
180 doing its best to avoid actually recompiling modules if their
181 external dependencies haven't changed. This is the same
182 mechanism we use to avoid re-compiling modules in the batch
183 compilation setting (see <xref linkend="recomp"/>).</para>
184 </sect2>
185 </sect1>
186
187 <sect1 id="ghci-compiled">
188 <title>Loading compiled code</title>
189 <indexterm><primary>compiled code</primary><secondary>in GHCi</secondary></indexterm>
190
191 <para>When you load a Haskell source module into GHCi, it is
192 normally converted to byte-code and run using the interpreter.
193 However, interpreted code can also run alongside compiled code in
194 GHCi; indeed, normally when GHCi starts, it loads up a compiled
195 copy of the <literal>base</literal> package, which contains the
196 <literal>Prelude</literal>.</para>
197
198 <para>Why should we want to run compiled code? Well, compiled
199 code is roughly 10x faster than interpreted code, but takes about
200 2x longer to produce (perhaps longer if optimisation is on). So
201 it pays to compile the parts of a program that aren't changing
202 very often, and use the interpreter for the code being actively
203 developed.</para>
204
205 <para>When loading up source files with <literal>:load</literal>,
206 GHCi looks for any corresponding compiled object files, and will
207 use one in preference to interpreting the source if possible. For
208 example, suppose we have a 4-module program consisting of modules
209 A, B, C, and D. Modules B and C both import D only,
210 and A imports both B &amp; C:</para>
211 <screen>
212 A
213 / \
214 B C
215 \ /
216 D
217 </screen>
218 <para>We can compile D, then load the whole program, like this:</para>
219 <screen>
220 Prelude> :! ghc -c D.hs
221 Prelude> :load A
222 Compiling B ( B.hs, interpreted )
223 Compiling C ( C.hs, interpreted )
224 Compiling A ( A.hs, interpreted )
225 Ok, modules loaded: A, B, C, D.
226 *Main>
227 </screen>
228
229 <para>In the messages from the compiler, we see that there is no line
230 for <literal>D</literal>. This is because
231 it isn't necessary to compile <literal>D</literal>,
232 because the source and everything it depends on
233 is unchanged since the last compilation.</para>
234
235 <para>At any time you can use the command
236 <literal>:show modules</literal>
237 to get a list of the modules currently loaded
238 into GHCi:</para>
239
240 <screen>
241 *Main> :show modules
242 D ( D.hs, D.o )
243 C ( C.hs, interpreted )
244 B ( B.hs, interpreted )
245 A ( A.hs, interpreted )
246 *Main></screen>
247
248 <para>If we now modify the source of D (or pretend to: using the Unix
249 command <literal>touch</literal> on the source file is handy for
250 this), the compiler will no longer be able to use the object file,
251 because it might be out of date:</para>
252
253 <screen>
254 *Main> :! touch D.hs
255 *Main> :reload
256 Compiling D ( D.hs, interpreted )
257 Ok, modules loaded: A, B, C, D.
258 *Main>
259 </screen>
260
261 <para>Note that module D was compiled, but in this instance
262 because its source hadn't really changed, its interface remained
263 the same, and the recompilation checker determined that A, B and C
264 didn't need to be recompiled.</para>
265
266 <para>So let's try compiling one of the other modules:</para>
267
268 <screen>
269 *Main> :! ghc -c C.hs
270 *Main> :load A
271 Compiling D ( D.hs, interpreted )
272 Compiling B ( B.hs, interpreted )
273 Compiling C ( C.hs, interpreted )
274 Compiling A ( A.hs, interpreted )
275 Ok, modules loaded: A, B, C, D.
276 </screen>
277
278 <para>We didn't get the compiled version of C! What happened?
279 Well, in GHCi a compiled module may only depend on other compiled
280 modules, and in this case C depends on D, which doesn't have an
281 object file, so GHCi also rejected C's object file. Ok, so let's
282 also compile D:</para>
283
284 <screen>
285 *Main> :! ghc -c D.hs
286 *Main> :reload
287 Ok, modules loaded: A, B, C, D.
288 </screen>
289
290 <para>Nothing happened! Here's another lesson: newly compiled
291 modules aren't picked up by <literal>:reload</literal>, only
292 <literal>:load</literal>:</para>
293
294 <screen>
295 *Main> :load A
296 Compiling B ( B.hs, interpreted )
297 Compiling A ( A.hs, interpreted )
298 Ok, modules loaded: A, B, C, D.
299 </screen>
300
301 <para>HINT: since GHCi will only use a compiled object file if it
302 can be sure that the compiled version is up-to-date, a good technique
303 when working on a large program is to occasionally run
304 <literal>ghc &ndash;&ndash;make</literal> to compile the whole project (say
305 before you go for lunch :-), then continue working in the
306 interpreter. As you modify code, the changed modules will be
307 interpreted, but the rest of the project will remain
308 compiled.</para>
309
310 </sect1>
311
312 <sect1 id="interactive-evaluation">
313 <title>Interactive evaluation at the prompt</title>
314
315 <para>When you type an expression at the prompt, GHCi immediately
316 evaluates and prints the result:
317 <screen>
318 Prelude> reverse "hello"
319 "olleh"
320 Prelude> 5+5
321 10
322 </screen>
323 </para>
324
325 <sect2><title>I/O actions at the prompt</title>
326
327 <para>GHCi does more than simple expression evaluation at the prompt.
328 If you type something of type <literal>IO a</literal> for some
329 <literal>a</literal>, then GHCi <emphasis>executes</emphasis> it
330 as an IO-computation.
331 <screen>
332 Prelude> "hello"
333 "hello"
334 Prelude> putStrLn "hello"
335 hello
336 </screen>
337 Furthermore, GHCi will print the result of the I/O action if (and only
338 if):
339 <itemizedlist>
340 <listitem><para>The result type is an instance of <literal>Show</literal>.</para></listitem>
341 <listitem><para>The result type is not
342 <literal>()</literal>.</para></listitem>
343 </itemizedlist>
344 For example, remembering that <literal>putStrLn :: String -> IO ()</literal>:
345 <screen>
346 Prelude> putStrLn "hello"
347 hello
348 Prelude> do { putStrLn "hello"; return "yes" }
349 hello
350 "yes"
351 </screen>
352 </para></sect2>
353
354 <sect2 id="ghci-stmts">
355 <title>Using <literal>do-</literal>notation at the prompt</title>
356 <indexterm><primary>do-notation</primary><secondary>in GHCi</secondary></indexterm>
357 <indexterm><primary>statements</primary><secondary>in GHCi</secondary></indexterm>
358
359 <para>GHCi actually accepts <firstterm>statements</firstterm>
360 rather than just expressions at the prompt. This means you can
361 bind values and functions to names, and use them in future
362 expressions or statements.</para>
363
364 <para>The syntax of a statement accepted at the GHCi prompt is
365 exactly the same as the syntax of a statement in a Haskell
366 <literal>do</literal> expression. However, there's no monad
367 overloading here: statements typed at the prompt must be in the
368 <literal>IO</literal> monad.
369 <screen>
370 Prelude> x &lt;- return 42
371 42
372 Prelude> print x
373 42
374 Prelude>
375 </screen>
376 The statement <literal>x &lt;- return 42</literal> means
377 &ldquo;execute <literal>return 42</literal> in the
378 <literal>IO</literal> monad, and bind the result to
379 <literal>x</literal>&rdquo;. We can then use
380 <literal>x</literal> in future statements, for example to print
381 it as we did above.</para>
382
383 <para>GHCi will print the result of a statement if and only if:
384 <itemizedlist>
385 <listitem>
386 <para>The statement is not a binding, or it is a monadic binding
387 (<literal>p &lt;- e</literal>) that binds exactly one
388 variable.</para>
389 </listitem>
390 <listitem>
391 <para>The variable's type is not polymorphic, is not
392 <literal>()</literal>, and is an instance of
393 <literal>Show</literal></para>
394 </listitem>
395 </itemizedlist>
396 The automatic printing of binding results can be supressed with
397 <option>:set -fno-print-bind-result</option> (this does not
398 supress printing the result of non-binding statements).
399 <indexterm><primary><option>-fno-print-bind-result</option></primary></indexterm><indexterm><primary><option>-fprint-bind-result</option></primary></indexterm>.
400 You might want to do this to prevent the result of binding
401 statements from being fully evaluated by the act of printing
402 them, for example.</para>
403
404 <para>Of course, you can also bind normal non-IO expressions
405 using the <literal>let</literal>-statement:</para>
406 <screen>
407 Prelude> let x = 42
408 Prelude> x
409 42
410 Prelude>
411 </screen>
412 <para>Another important difference between the two types of binding
413 is that the monadic bind (<literal>p &lt;- e</literal>) is
414 <emphasis>strict</emphasis> (it evaluates <literal>e</literal>),
415 whereas with the <literal>let</literal> form, the expression
416 isn't evaluated immediately:</para>
417 <screen>
418 Prelude> let x = error "help!"
419 Prelude> print x
420 *** Exception: help!
421 Prelude>
422 </screen>
423
424 <para>Note that <literal>let</literal> bindings do not automatically
425 print the value bound, unlike monadic bindings.</para>
426
427 <para>Any exceptions raised during the evaluation or execution
428 of the statement are caught and printed by the GHCi command line
429 interface (for more information on exceptions, see the module
430 <literal>Control.Exception</literal> in the libraries
431 documentation).</para>
432
433 <para>Every new binding shadows any existing bindings of the
434 same name, including entities that are in scope in the current
435 module context.</para>
436
437 <para>WARNING: temporary bindings introduced at the prompt only
438 last until the next <literal>:load</literal> or
439 <literal>:reload</literal> command, at which time they will be
440 simply lost. However, they do survive a change of context with
441 <literal>:module</literal>: the temporary bindings just move to
442 the new location.</para>
443
444 <para>HINT: To get a list of the bindings currently in scope, use the
445 <literal>:show bindings</literal> command:</para>
446
447 <screen>
448 Prelude> :show bindings
449 x :: Int
450 Prelude></screen>
451
452 <para>HINT: if you turn on the <literal>+t</literal> option,
453 GHCi will show the type of each variable bound by a statement.
454 For example:</para>
455 <indexterm><primary><literal>+t</literal></primary></indexterm>
456 <screen>
457 Prelude> :set +t
458 Prelude> let (x:xs) = [1..]
459 x :: Integer
460 xs :: [Integer]
461 </screen>
462
463 </sect2>
464
465 <sect2 id="ghci-scope">
466 <title>What's really in scope at the prompt?</title>
467
468 <para>When you type an expression at the prompt, what
469 identifiers and types are in scope? GHCi provides a flexible
470 way to control exactly how the context for an expression is
471 constructed. Let's start with the simple cases; when you start
472 GHCi the prompt looks like this:</para>
473
474 <screen>Prelude></screen>
475
476 <para>Which indicates that everything from the module
477 <literal>Prelude</literal> is currently in scope. If we now
478 load a file into GHCi, the prompt will change:</para>
479
480 <screen>
481 Prelude> :load Main.hs
482 Compiling Main ( Main.hs, interpreted )
483 *Main>
484 </screen>
485
486 <para>The new prompt is <literal>*Main</literal>, which
487 indicates that we are typing expressions in the context of the
488 top-level of the <literal>Main</literal> module. Everything
489 that is in scope at the top-level in the module
490 <literal>Main</literal> we just loaded is also in scope at the
491 prompt (probably including <literal>Prelude</literal>, as long
492 as <literal>Main</literal> doesn't explicitly hide it).</para>
493
494 <para>The syntax
495 <literal>*<replaceable>module</replaceable></literal> indicates
496 that it is the full top-level scope of
497 <replaceable>module</replaceable> that is contributing to the
498 scope for expressions typed at the prompt. Without the
499 <literal>*</literal>, just the exports of the module are
500 visible.</para>
501
502 <para>We're not limited to a single module: GHCi can combine
503 scopes from multiple modules, in any mixture of
504 <literal>*</literal> and non-<literal>*</literal> forms. GHCi
505 combines the scopes from all of these modules to form the scope
506 that is in effect at the prompt. For technical reasons, GHCi
507 can only support the <literal>*</literal>-form for modules which
508 are interpreted, so compiled modules and package modules can
509 only contribute their exports to the current scope.</para>
510
511 <para>The scope is manipulated using the
512 <literal>:module</literal> command. For example, if the current
513 scope is <literal>Prelude</literal>, then we can bring into
514 scope the exports from the module <literal>IO</literal> like
515 so:</para>
516
517 <screen>
518 Prelude> :module +IO
519 Prelude IO> hPutStrLn stdout "hello\n"
520 hello
521 Prelude IO>
522 </screen>
523
524 <para>(Note: you can use <literal>import M</literal> as an
525 alternative to <literal>:module +M</literal>, and
526 <literal>:module</literal> can also be shortened to
527 <literal>:m</literal>). The full syntax of the
528 <literal>:module</literal> command is:</para>
529
530 <screen>
531 :module <optional>+|-</optional> <optional>*</optional><replaceable>mod<subscript>1</subscript></replaceable> ... <optional>*</optional><replaceable>mod<subscript>n</subscript></replaceable>
532 </screen>
533
534 <para>Using the <literal>+</literal> form of the
535 <literal>module</literal> commands adds modules to the current
536 scope, and <literal>-</literal> removes them. Without either
537 <literal>+</literal> or <literal>-</literal>, the current scope
538 is replaced by the set of modules specified. Note that if you
539 use this form and leave out <literal>Prelude</literal>, GHCi
540 will assume that you really wanted the
541 <literal>Prelude</literal> and add it in for you (if you don't
542 want the <literal>Prelude</literal>, then ask to remove it with
543 <literal>:m -Prelude</literal>).</para>
544
545 <para>The scope is automatically set after a
546 <literal>:load</literal> command, to the most recently loaded
547 "target" module, in a <literal>*</literal>-form if possible.
548 For example, if you say <literal>:load foo.hs bar.hs</literal>
549 and <filename>bar.hs</filename> contains module
550 <literal>Bar</literal>, then the scope will be set to
551 <literal>*Bar</literal> if <literal>Bar</literal> is
552 interpreted, or if <literal>Bar</literal> is compiled it will be
553 set to <literal>Prelude Bar</literal> (GHCi automatically adds
554 <literal>Prelude</literal> if it isn't present and there aren't
555 any <literal>*</literal>-form modules).</para>
556
557 <para>With multiple modules in scope, especially multiple
558 <literal>*</literal>-form modules, it is likely that name
559 clashes will occur. Haskell specifies that name clashes are
560 only reported when an ambiguous identifier is used, and GHCi
561 behaves in the same way for expressions typed at the
562 prompt.</para>
563
564 <para>
565 Hint: GHCi will tab-complete names that are in scope; for
566 example, if you run GHCi and type <literal>J&lt;tab&gt;</literal>
567 then GHCi will expand it to &ldquo;<literal>Just </literal>&rdquo;.
568 </para>
569
570 <sect3>
571 <title>Qualified names</title>
572
573 <para>To make life slightly easier, the GHCi prompt also
574 behaves as if there is an implicit <literal>import
575 qualified</literal> declaration for every module in every
576 package, and every module currently loaded into GHCi.</para>
577 </sect3>
578
579 <sect3>
580 <title>The <literal>:main</literal> command</title>
581
582 <para>
583 When a program is compiled and executed, it can use the
584 <literal>getArgs</literal> function to access the
585 command-line arguments.
586 However, we cannot simply pass the arguments to the
587 <literal>main</literal> function while we are testing in ghci,
588 as the <literal>main</literal> function doesn't take its
589 directly.
590 </para>
591
592 <para>
593 Instead, we can use the <literal>:main</literal> command.
594 This runs whatever <literal>main</literal> is in scope, with
595 any arguments being treated the same as command-line arguments,
596 e.g.:
597 </para>
598
599 <screen>
600 Prelude> let main = System.Environment.getArgs >>= print
601 Prelude> :main foo bar
602 ["foo","bar"]
603 </screen>
604
605 </sect3>
606 </sect2>
607
608
609 <sect2>
610 <title>The <literal>it</literal> variable</title>
611 <indexterm><primary><literal>it</literal></primary>
612 </indexterm>
613
614 <para>Whenever an expression (or a non-binding statement, to be
615 precise) is typed at the prompt, GHCi implicitly binds its value
616 to the variable <literal>it</literal>. For example:</para>
617 <screen>
618 Prelude> 1+2
619 3
620 Prelude> it * 2
621 6
622 </screen>
623 <para>What actually happens is that GHCi typechecks the
624 expression, and if it doesn't have an <literal>IO</literal> type,
625 then it transforms it as follows: an expression
626 <replaceable>e</replaceable> turns into
627 <screen>
628 let it = <replaceable>e</replaceable>;
629 print it
630 </screen>
631 which is then run as an IO-action.</para>
632
633 <para>Hence, the original expression must have a type which is an
634 instance of the <literal>Show</literal> class, or GHCi will
635 complain:</para>
636
637 <screen>
638 Prelude&gt; id
639
640 &lt;interactive&gt;:1:0:
641 No instance for (Show (a -&gt; a))
642 arising from use of `print' at &lt;interactive&gt;:1:0-1
643 Possible fix: add an instance declaration for (Show (a -> a))
644 In the expression: print it
645 In a 'do' expression: print it
646 </screen>
647
648 <para>The error message contains some clues as to the
649 transformation happening internally.</para>
650
651 <para>If the expression was instead of type <literal>IO a</literal> for
652 some <literal>a</literal>, then <literal>it</literal> will be
653 bound to the result of the <literal>IO</literal> computation,
654 which is of type <literal>a</literal>. eg.:</para>
655 <screen>
656 Prelude> Time.getClockTime
657 Wed Mar 14 12:23:13 GMT 2001
658 Prelude> print it
659 Wed Mar 14 12:23:13 GMT 2001
660 </screen>
661
662 <para>The corresponding translation for an IO-typed
663 <replaceable>e</replaceable> is
664 <screen>
665 it &lt;- <replaceable>e</replaceable>
666 </screen>
667 </para>
668
669 <para>Note that <literal>it</literal> is shadowed by the new
670 value each time you evaluate a new expression, and the old value
671 of <literal>it</literal> is lost.</para>
672
673 </sect2>
674
675 <sect2 id="extended-default-rules">
676 <title>Type defaulting in GHCi</title>
677 <indexterm><primary>Type default</primary></indexterm>
678 <indexterm><primary><literal>Show</literal> class</primary></indexterm>
679 <para>
680 Consider this GHCi session:
681 <programlisting>
682 ghci> reverse []
683 </programlisting>
684 What should GHCi do? Strictly speaking, the program is ambiguous. <literal>show (reverse [])</literal>
685 (which is what GHCi computes here) has type <literal>Show a => a</literal> and how that displays depends
686 on the type <literal>a</literal>. For example:
687 <programlisting>
688 ghci> (reverse []) :: String
689 ""
690 ghci> (reverse []) :: [Int]
691 []
692 </programlisting>
693 However, it is tiresome for the user to have to specify the type, so GHCi extends Haskell's type-defaulting
694 rules (Section 4.3.4 of the Haskell 98 Report (Revised)) as follows. The
695 standard rules take each group of constraints <literal>(C1 a, C2 a, ..., Cn
696 a)</literal> for each type variable <literal>a</literal>, and defaults the
697 type variable if
698 <orderedlist>
699 <listitem>
700 <para>
701 The type variable <literal>a</literal> appears in no
702 other constraints
703 </para>
704 </listitem>
705 <listitem>
706 <para>
707 All the classes <literal>Ci</literal> are standard.
708 </para>
709 </listitem>
710 <listitem>
711 <para>
712 At least one of the classes <literal>Ci</literal> is
713 numeric.
714 </para>
715 </listitem>
716 </orderedlist>
717 At the GHCi prompt, or with GHC if the
718 <literal>-XExtendedDefaultRules</literal> flag is given,
719 the following additional differences apply:
720 <itemizedlist>
721 <listitem>
722 <para>
723 Rule 2 above is relaxed thus:
724 <emphasis>All</emphasis> of the classes
725 <literal>Ci</literal> are single-parameter type classes.
726 </para>
727 </listitem>
728 <listitem>
729 <para>
730 Rule 3 above is relaxed this:
731 At least one of the classes <literal>Ci</literal> is
732 numeric, <emphasis>or is <literal>Show</literal>,
733 <literal>Eq</literal>, or
734 <literal>Ord</literal></emphasis>.
735 </para>
736 </listitem>
737 <listitem>
738 <para>
739 The unit type <literal>()</literal> is added to the
740 start of the standard list of types which are tried when
741 doing type defaulting.
742 </para>
743 </listitem>
744 </itemizedlist>
745 The last point means that, for example, this program:
746 <programlisting>
747 main :: IO ()
748 main = print def
749
750 instance Num ()
751
752 def :: (Num a, Enum a) => a
753 def = toEnum 0
754 </programlisting>
755 prints <literal>()</literal> rather than <literal>0</literal> as the
756 type is defaulted to <literal>()</literal> rather than
757 <literal>Integer</literal>.
758 </para>
759 <para>
760 The motivation for the change is that it means <literal>IO a</literal>
761 actions default to <literal>IO ()</literal>, which in turn means that
762 ghci won't try to print a result when running them. This is
763 particularly important for <literal>printf</literal>, which has an
764 instance that returns <literal>IO a</literal>.
765 However, it is only able to return
766 <literal>undefined</literal>
767 (the reason for the instance having this type is so that printf
768 doesn't require extensions to the class system), so if the type defaults to
769 <literal>Integer</literal> then ghci gives an error when running a
770 printf.
771 </para>
772 </sect2>
773 </sect1>
774
775 <sect1 id="ghci-debugger">
776 <title>The GHCi Debugger</title>
777 <indexterm><primary>debugger</primary><secondary>in GHCi</secondary>
778 </indexterm>
779
780 <para>GHCi contains a simple imperative-style debugger in which you can
781 stop a running computation in order to examine the values of
782 variables. The debugger is integrated into GHCi, and is turned on by
783 default: no flags are required to enable the debugging facilities. There
784 is one major restriction: breakpoints and single-stepping are only
785 available in <emphasis>interpreted</emphasis> modules; compiled code is
786 invisible to the debugger.</para>
787
788 <para>The debugger provides the following:
789 <itemizedlist>
790 <listitem>
791 <para>The ability to set a <firstterm>breakpoint</firstterm> on a
792 function definition or expression in the program. When the function
793 is called, or the expression evaluated, GHCi suspends
794 execution and returns to the prompt, where you can inspect the
795 values of local variables before continuing with the
796 execution.</para>
797 </listitem>
798 <listitem>
799 <para>Execution can be <firstterm>single-stepped</firstterm>: the
800 evaluator will suspend execution approximately after every
801 reduction, allowing local variables to be inspected. This is
802 equivalent to setting a breakpoint at every point in the
803 program.</para>
804 </listitem>
805 <listitem>
806 <para>Execution can take place in <firstterm>tracing
807 mode</firstterm>, in which the evaluator remembers each
808 evaluation step as it happens, but doesn't suspend execution until
809 an actual breakpoint is reached. When this happens, the history of
810 evaluation steps can be inspected.</para>
811 </listitem>
812 <listitem>
813 <para>Exceptions (e.g. pattern matching failure and
814 <literal>error</literal>) can be treated as breakpoints, to help
815 locate the source of an exception in the program.</para>
816 </listitem>
817 </itemizedlist>
818 </para>
819
820 <para>There is currently no support for obtaining a &ldquo;stack
821 trace&rdquo;, but the tracing and history features provide a useful
822 second-best, which will often be enough to establish the context of an
823 error.</para>
824
825 <sect2 id="breakpoints">
826 <title>Breakpoints and inspecting variables</title>
827
828 <para>Let's use quicksort as a running example. Here's the code:</para>
829
830 <programlisting>
831 qsort [] = []
832 qsort (a:as) = qsort left ++ [a] ++ qsort right
833 where (left,right) = (filter (&lt;=a) as, filter (&gt;a) as)
834
835 main = print (qsort [8, 4, 0, 3, 1, 23, 11, 18])
836 </programlisting>
837
838 <para>First, load the module into GHCi:</para>
839
840 <screen>
841 Prelude> :l qsort.hs
842 [1 of 1] Compiling Main ( qsort.hs, interpreted )
843 Ok, modules loaded: Main.
844 *Main>
845 </screen>
846
847 <para>Now, let's set a breakpoint on the right-hand-side of the second
848 equation of qsort:</para>
849
850 <programlisting>
851 *Main> :break 2
852 Breakpoint 0 activated at qsort.hs:2:15-46
853 *Main>
854 </programlisting>
855
856 <para>The command <literal>:break 2</literal> sets a breakpoint on line
857 2 of the most recently-loaded module, in this case
858 <literal>qsort.hs</literal>. Specifically, it picks the
859 leftmost complete subexpression on that line on which to set the
860 breakpoint, which in this case is the expression
861 <literal>(qsort left ++ [a] ++ qsort right)</literal>.</para>
862
863 <para>Now, we run the program:</para>
864
865 <programlisting>
866 *Main> main
867 Stopped at qsort.hs:2:15-46
868 _result :: [a]
869 a :: a
870 left :: [a]
871 right :: [a]
872 [qsort.hs:2:15-46] *Main>
873 </programlisting>
874
875 <para>Execution has stopped at the breakpoint. The prompt has changed to
876 indicate that we are currently stopped at a breakpoint, and the location:
877 <literal>[qsort.hs:2:15-46]</literal>. To further clarify the
878 location, we can use the <literal>:list</literal> command:</para>
879
880 <programlisting>
881 [qsort.hs:2:15-46] *Main> :list
882 1 qsort [] = []
883 2 qsort (a:as) = qsort left ++ [a] ++ qsort right
884 3 where (left,right) = (filter (&lt;=a) as, filter (&gt;a) as)
885 </programlisting>
886
887 <para>The <literal>:list</literal> command lists the source code around
888 the current breakpoint. If your output device supports it, then GHCi
889 will highlight the active subexpression in bold.</para>
890
891 <para>GHCi has provided bindings for the free variables<footnote><para>We
892 originally provided bindings for all variables in scope, rather
893 than just
894 the free variables of the expression, but found that this affected
895 performance considerably, hence the current restriction to just the
896 free variables.</para>
897 </footnote> of the expression
898 on which the
899 breakpoint was placed (<literal>a</literal>, <literal>left</literal>,
900 <literal>right</literal>), and additionally a binding for the result of
901 the expression (<literal>_result</literal>). These variables are just
902 like other variables that you might define in GHCi; you
903 can use them in expressions that you type at the prompt, you can ask
904 for their types with <literal>:type</literal>, and so on. There is one
905 important difference though: these variables may only have partial
906 types. For example, if we try to display the value of
907 <literal>left</literal>:</para>
908
909 <screen>
910 [qsort.hs:2:15-46] *Main> left
911
912 &lt;interactive&gt;:1:0:
913 Ambiguous type variable `a' in the constraint:
914 `Show a' arising from a use of `print' at &lt;interactive&gt;:1:0-3
915 Cannot resolve unknown runtime types: a
916 Use :print or :force to determine these types
917 </screen>
918
919 <para>This is because <literal>qsort</literal> is a polymorphic function,
920 and because GHCi does not carry type information at runtime, it cannot
921 determine the runtime types of free variables that involve type
922 variables. Hence, when you ask to display <literal>left</literal> at
923 the prompt, GHCi can't figure out which instance of
924 <literal>Show</literal> to use, so it emits the type error above.</para>
925
926 <para>Fortunately, the debugger includes a generic printing command,
927 <literal>:print</literal>, which can inspect the actual runtime value of a
928 variable and attempt to reconstruct its type. If we try it on
929 <literal>left</literal>:</para>
930
931 <screen>
932 [qsort.hs:2:15-46] *Main> :print left
933 left = (_t1::[a])
934 </screen>
935
936 <para>This isn't particularly enlightening. What happened is that
937 <literal>left</literal> is bound to an unevaluated computation (a
938 suspension, or <firstterm>thunk</firstterm>), and
939 <literal>:print</literal> does not force any evaluation. The idea is
940 that <literal>:print</literal> can be used to inspect values at a
941 breakpoint without any unfortunate side effects. It won't force any
942 evaluation, which could cause the program to give a different answer
943 than it would normally, and hence it won't cause any exceptions to be
944 raised, infinite loops, or further breakpoints to be triggered (see
945 <xref linkend="nested-breakpoints" />).
946 Rather than forcing thunks, <literal>:print</literal>
947 binds each thunk to a fresh variable beginning with an
948 underscore, in this case
949 <literal>_t1</literal>.</para>
950
951 <para>If we aren't concerned about preserving the evaluatedness of a
952 variable, we can use <literal>:force</literal> instead of
953 <literal>:print</literal>. The <literal>:force</literal> command
954 behaves exactly like <literal>:print</literal>, except that it forces
955 the evaluation of any thunks it encounters:</para>
956
957 <screen>
958 [qsort.hs:2:15-46] *Main> :force left
959 left = [4,0,3,1]
960 </screen>
961
962 <para>Now, since <literal>:force</literal> has inspected the runtime
963 value of <literal>left</literal>, it has reconstructed its type. We
964 can see the results of this type reconstruction:</para>
965
966 <screen>
967 [qsort.hs:2:15-46] *Main> :show bindings
968 _result :: [Integer]
969 a :: Integer
970 left :: [Integer]
971 right :: [Integer]
972 _t1 :: [Integer]
973 </screen>
974
975 <para>Not only do we now know the type of <literal>left</literal>, but
976 all the other partial types have also been resolved. So we can ask
977 for the value of <literal>a</literal>, for example:</para>
978
979 <screen>
980 [qsort.hs:2:15-46] *Main> a
981 8
982 </screen>
983
984 <para>You might find it useful to use Haskell's
985 <literal>seq</literal> function to evaluate individual thunks rather
986 than evaluating the whole expression with <literal>:force</literal>.
987 For example:</para>
988
989 <screen>
990 [qsort.hs:2:15-46] *Main> :print right
991 right = (_t1::[Integer])
992 [qsort.hs:2:15-46] *Main> seq _t1 ()
993 ()
994 [qsort.hs:2:15-46] *Main> :print right
995 right = 23 : (_t2::[Integer])
996 </screen>
997
998 <para>We evaluated only the <literal>_t1</literal> thunk, revealing the
999 head of the list, and the tail is another thunk now bound to
1000 <literal>_t2</literal>. The <literal>seq</literal> function is a
1001 little inconvenient to use here, so you might want to use
1002 <literal>:def</literal> to make a nicer interface (left as an exercise
1003 for the reader!).</para>
1004
1005 <para>Finally, we can continue the current execution:</para>
1006
1007 <screen>
1008 [qsort.hs:2:15-46] *Main> :continue
1009 Stopped at qsort.hs:2:15-46
1010 _result :: [a]
1011 a :: a
1012 left :: [a]
1013 right :: [a]
1014 [qsort.hs:2:15-46] *Main>
1015 </screen>
1016
1017 <para>The execution continued at the point it previously stopped, and has
1018 now stopped at the breakpoint for a second time.</para>
1019
1020 <sect3 id="setting-breakpoints">
1021 <title>Setting breakpoints</title>
1022
1023 <para>Breakpoints can be set in various ways. Perhaps the easiest way to
1024 set a breakpoint is to name a top-level function:</para>
1025
1026 <screen>
1027 :break <replaceable>identifier</replaceable>
1028 </screen>
1029
1030 <para>Where <replaceable>identifier</replaceable> names any top-level
1031 function in an interpreted module currently loaded into GHCi (qualified
1032 names may be used). The breakpoint will be set on the body of the
1033 function, when it is fully applied but before any pattern matching has
1034 taken place.</para>
1035
1036 <para>Breakpoints can also be set by line (and optionally column)
1037 number:</para>
1038
1039 <screen>
1040 :break <replaceable>line</replaceable>
1041 :break <replaceable>line</replaceable> <replaceable>column</replaceable>
1042 :break <replaceable>module</replaceable> <replaceable>line</replaceable>
1043 :break <replaceable>module</replaceable> <replaceable>line</replaceable> <replaceable>column</replaceable>
1044 </screen>
1045
1046 <para>When a breakpoint is set on a particular line, GHCi sets the
1047 breakpoint on the
1048 leftmost subexpression that begins and ends on that line. If two
1049 complete subexpressions start at the same
1050 column, the longest one is picked. If there is no complete
1051 subexpression on the line, then the leftmost expression starting on
1052 the line is picked, and failing that the rightmost expression that
1053 partially or completely covers the line.</para>
1054
1055 <para>When a breakpoint is set on a particular line and column, GHCi
1056 picks the smallest subexpression that encloses that location on which
1057 to set the breakpoint. Note: GHC considers the TAB character to have a
1058 width of 1, wherever it occurs; in other words it counts
1059 characters, rather than columns. This matches what some editors do,
1060 and doesn't match others. The best advice is to avoid tab
1061 characters in your source code altogether (see
1062 <option>-fwarn-tabs</option> in <xref linkend="options-sanity"
1063 />).</para>
1064
1065 <para>If the module is omitted, then the most recently-loaded module is
1066 used.</para>
1067
1068 <para>Not all subexpressions are potential breakpoint locations. Single
1069 variables are typically not considered to be breakpoint locations
1070 (unless the variable is the right-hand-side of a function definition,
1071 lambda, or case alternative). The rule of thumb is that all redexes
1072 are breakpoint locations, together with the bodies of functions,
1073 lambdas, case alternatives and binding statements. There is normally
1074 no breakpoint on a let expression, but there will always be a
1075 breakpoint on its body, because we are usually interested in inspecting
1076 the values of the variables bound by the let.</para>
1077
1078 </sect3>
1079 <sect3>
1080 <title>Listing and deleting breakpoints</title>
1081
1082 <para>The list of breakpoints currently enabled can be displayed using
1083 <literal>:show&nbsp;breaks</literal>:</para>
1084 <screen>
1085 *Main> :show breaks
1086 [0] Main qsort.hs:1:11-12
1087 [1] Main qsort.hs:2:15-46
1088 </screen>
1089
1090 <para>To delete a breakpoint, use the <literal>:delete</literal>
1091 command with the number given in the output from <literal>:show&nbsp;breaks</literal>:</para>
1092
1093 <screen>
1094 *Main> :delete 0
1095 *Main> :show breaks
1096 [1] Main qsort.hs:2:15-46
1097 </screen>
1098
1099 <para>To delete all breakpoints at once, use <literal>:delete *</literal>.</para>
1100
1101 </sect3>
1102 </sect2>
1103
1104 <sect2 id="single-stepping">
1105 <title>Single-stepping</title>
1106
1107 <para>Single-stepping is a great way to visualise the execution of your
1108 program, and it is also a useful tool for identifying the source of a
1109 bug. GHCi offers two variants of stepping. Use
1110 <literal>:step</literal> to enable all the
1111 breakpoints in the program, and execute until the next breakpoint is
1112 reached. Use <literal>:steplocal</literal> to limit the set
1113 of enabled breakpoints to those in the current top level function.
1114 Similarly, use <literal>:stepmodule</literal> to single step only on
1115 breakpoints contained in the current module.
1116 For example:</para>
1117
1118 <screen>
1119 *Main> :step main
1120 Stopped at qsort.hs:5:7-47
1121 _result :: IO ()
1122 </screen>
1123
1124 <para>The command <literal>:step
1125 <replaceable>expr</replaceable></literal> begins the evaluation of
1126 <replaceable>expr</replaceable> in single-stepping mode. If
1127 <replaceable>expr</replaceable> is ommitted, then it single-steps from
1128 the current breakpoint. <literal>:stepover</literal>
1129 works similarly.</para>
1130
1131 <para>The <literal>:list</literal> command is particularly useful when
1132 single-stepping, to see where you currently are:</para>
1133
1134 <screen>
1135 [qsort.hs:5:7-47] *Main> :list
1136 4
1137 5 main = print (qsort [8, 4, 0, 3, 1, 23, 11, 18])
1138 6
1139 [qsort.hs:5:7-47] *Main>
1140 </screen>
1141
1142 <para>In fact, GHCi provides a way to run a command when a breakpoint is
1143 hit, so we can make it automatically do
1144 <literal>:list</literal>:</para>
1145
1146 <screen>
1147 [qsort.hs:5:7-47] *Main> :set stop :list
1148 [qsort.hs:5:7-47] *Main> :step
1149 Stopped at qsort.hs:5:14-46
1150 _result :: [Integer]
1151 4
1152 5 main = print (qsort [8, 4, 0, 3, 1, 23, 11, 18])
1153 6
1154 [qsort.hs:5:14-46] *Main>
1155 </screen>
1156 </sect2>
1157
1158 <sect2 id="nested-breakpoints">
1159 <title>Nested breakpoints</title>
1160 <para>When GHCi is stopped at a breakpoint, and an expression entered at
1161 the prompt triggers a
1162 second breakpoint, the new breakpoint becomes the &ldquo;current&rdquo;
1163 one, and the old one is saved on a stack. An arbitrary number of
1164 breakpoint contexts can be built up in this way. For example:</para>
1165
1166 <screen>
1167 [qsort.hs:2:15-46] *Main> :st qsort [1,3]
1168 Stopped at qsort.hs:(1,0)-(3,55)
1169 _result :: [a]
1170 ... [qsort.hs:(1,0)-(3,55)] *Main>
1171 </screen>
1172
1173 <para>While stopped at the breakpoint on line 2 that we set earlier, we
1174 started a new evaluation with <literal>:step qsort [1,3]</literal>.
1175 This new evaluation stopped after one step (at the definition of
1176 <literal>qsort</literal>). The prompt has changed, now prefixed with
1177 <literal>...</literal>, to indicate that there are saved breakpoints
1178 beyond the current one. To see the stack of contexts, use
1179 <literal>:show context</literal>:</para>
1180
1181 <screen>
1182 ... [qsort.hs:(1,0)-(3,55)] *Main> :show context
1183 --> main
1184 Stopped at qsort.hs:2:15-46
1185 --> qsort [1,3]
1186 Stopped at qsort.hs:(1,0)-(3,55)
1187 ... [qsort.hs:(1,0)-(3,55)] *Main>
1188 </screen>
1189
1190 <para>To abandon the current evaluation, use
1191 <literal>:abandon</literal>:</para>
1192
1193 <screen>
1194 ... [qsort.hs:(1,0)-(3,55)] *Main> :abandon
1195 [qsort.hs:2:15-46] *Main> :abandon
1196 *Main>
1197 </screen>
1198 </sect2>
1199
1200 <sect2 id="ghci-debugger-result">
1201 <title>The <literal>_result</literal> variable</title>
1202 <para>When stopped at a breakpoint or single-step, GHCi binds the
1203 variable <literal>_result</literal> to the value of the currently
1204 active expression. The value of <literal>_result</literal> is
1205 presumably not available yet, because we stopped its evaluation, but it
1206 can be forced: if the type is known and showable, then just entering
1207 <literal>_result</literal> at the prompt will show it. However,
1208 there's one caveat to doing this: evaluating <literal>_result</literal>
1209 will be likely to trigger further breakpoints, starting with the
1210 breakpoint we are currently stopped at (if we stopped at a real
1211 breakpoint, rather than due to <literal>:step</literal>). So it will
1212 probably be necessary to issue a <literal>:continue</literal>
1213 immediately when evaluating <literal>_result</literal>. Alternatively,
1214 you can use <literal>:force</literal> which ignores breakpoints.</para>
1215 </sect2>
1216
1217 <sect2 id="tracing">
1218 <title>Tracing and history</title>
1219
1220 <para>A question that we often want to ask when debugging a program is
1221 &ldquo;how did I get here?&rdquo;. Traditional imperative debuggers
1222 usually provide some kind of stack-tracing feature that lets you see
1223 the stack of active function calls (sometimes called the &ldquo;lexical
1224 call stack&rdquo;), describing a path through the code
1225 to the current location. Unfortunately this is hard to provide in
1226 Haskell, because execution proceeds on a demand-driven basis, rather
1227 than a depth-first basis as in strict languages. The
1228 &ldquo;stack&ldquo; in GHC's execution engine bears little
1229 resemblance to the lexical call stack. Ideally GHCi would maintain a
1230 separate lexical call stack in addition to the dynamic call stack, and
1231 in fact this is exactly
1232 what our profiling system does (<xref linkend="profiling" />), and what
1233 some other Haskell debuggers do. For the time being, however, GHCi
1234 doesn't maintain a lexical call stack (there are some technical
1235 challenges to be overcome). Instead, we provide a way to backtrack from a
1236 breakpoint to previous evaluation steps: essentially this is like
1237 single-stepping backwards, and should in many cases provide enough
1238 information to answer the &ldquo;how did I get here?&rdquo;
1239 question.</para>
1240
1241 <para>To use tracing, evaluate an expression with the
1242 <literal>:trace</literal> command. For example, if we set a breakpoint
1243 on the base case of <literal>qsort</literal>:</para>
1244
1245 <screen>
1246 *Main&gt; :list qsort
1247 1 qsort [] = []
1248 2 qsort (a:as) = qsort left ++ [a] ++ qsort right
1249 3 where (left,right) = (filter (&lt;=a) as, filter (&gt;a) as)
1250 4
1251 *Main&gt; :b 1
1252 Breakpoint 1 activated at qsort.hs:1:11-12
1253 *Main&gt;
1254 </screen>
1255
1256 <para>and then run a small <literal>qsort</literal> with
1257 tracing:</para>
1258
1259 <screen>
1260 *Main> :trace qsort [3,2,1]
1261 Stopped at qsort.hs:1:11-12
1262 _result :: [a]
1263 [qsort.hs:1:11-12] *Main>
1264 </screen>
1265
1266 <para>We can now inspect the history of evaluation steps:</para>
1267
1268 <screen>
1269 [qsort.hs:1:11-12] *Main> :hist
1270 -1 : qsort.hs:3:24-38
1271 -2 : qsort.hs:3:23-55
1272 -3 : qsort.hs:(1,0)-(3,55)
1273 -4 : qsort.hs:2:15-24
1274 -5 : qsort.hs:2:15-46
1275 -6 : qsort.hs:3:24-38
1276 -7 : qsort.hs:3:23-55
1277 -8 : qsort.hs:(1,0)-(3,55)
1278 -9 : qsort.hs:2:15-24
1279 -10 : qsort.hs:2:15-46
1280 -11 : qsort.hs:3:24-38
1281 -12 : qsort.hs:3:23-55
1282 -13 : qsort.hs:(1,0)-(3,55)
1283 -14 : qsort.hs:2:15-24
1284 -15 : qsort.hs:2:15-46
1285 -16 : qsort.hs:(1,0)-(3,55)
1286 &lt;end of history&gt;
1287 </screen>
1288
1289 <para>To examine one of the steps in the history, use
1290 <literal>:back</literal>:</para>
1291
1292 <screen>
1293 [qsort.hs:1:11-12] *Main> :back
1294 Logged breakpoint at qsort.hs:3:24-38
1295 _result :: [a]
1296 as :: [a]
1297 a :: a
1298 [-1: qsort.hs:3:24-38] *Main>
1299 </screen>
1300
1301 <para>Note that the local variables at each step in the history have been
1302 preserved, and can be examined as usual. Also note that the prompt has
1303 changed to indicate that we're currently examining the first step in
1304 the history: <literal>-1</literal>. The command
1305 <literal>:forward</literal> can be used to traverse forward in the
1306 history.</para>
1307
1308 <para>The <literal>:trace</literal> command can be used with or without
1309 an expression. When used without an expression, tracing begins from
1310 the current breakpoint, just like <literal>:step</literal>.</para>
1311
1312 <para>The history is only available when
1313 using <literal>:trace</literal>; the reason for this is we found that
1314 logging each breakpoint in the history cuts performance by a factor of
1315 2 or more. GHCi remembers the last 50 steps in the history (perhaps in
1316 the future we'll make this configurable).</para>
1317 </sect2>
1318
1319 <sect2 id="ghci-debugger-exceptions">
1320 <title>Debugging exceptions</title>
1321 <para>Another common question that comes up when debugging is
1322 &ldquo;where did this exception come from?&rdquo;. Exceptions such as
1323 those raised by <literal>error</literal> or <literal>head []</literal>
1324 have no context information attached to them. Finding which
1325 particular call to <literal>head</literal> in your program resulted in
1326 the error can be a painstaking process, usually involving
1327 <literal>Debug.Trace.trace</literal>, or compiling with
1328 profiling and using <literal>+RTS -xc</literal> (see <xref
1329 linkend="prof-time-options" />).</para>
1330
1331 <para>The GHCi debugger offers a way to hopefully shed some light on
1332 these errors quickly and without modifying or recompiling the source
1333 code. One way would be to set a breakpoint on the location in the
1334 source code that throws the exception, and then use
1335 <literal>:trace</literal> and <literal>:history</literal> to establish
1336 the context. However, <literal>head</literal> is in a library and
1337 we can't set a breakpoint on it directly. For this reason, GHCi
1338 provides the flag <literal>-fbreak-on-exception</literal> which causes
1339 the evaluator to stop when an exception is thrown, just as it does when
1340 a breakpoint is hit. This is only really useful in conjunction with
1341 <literal>:trace</literal>, in order to log the steps leading up to the
1342 exception. For example:</para>
1343
1344 <screen>
1345 *Main> :set -fbreak-on-exception
1346 *Main> :trace qsort ("abc" ++ undefined)
1347 "Stopped at &lt;exception thrown&gt;
1348 _exception :: e
1349 [&lt;exception thrown&gt;] *Main&gt; :hist
1350 -1 : qsort.hs:3:24-38
1351 -2 : qsort.hs:3:23-55
1352 -3 : qsort.hs:(1,0)-(3,55)
1353 -4 : qsort.hs:2:15-24
1354 -5 : qsort.hs:2:15-46
1355 -6 : qsort.hs:(1,0)-(3,55)
1356 &lt;end of history&gt;
1357 [&lt;exception thrown&gt;] *Main&gt; :back
1358 Logged breakpoint at qsort.hs:3:24-38
1359 _result :: [a]
1360 as :: [a]
1361 a :: a
1362 [-1: qsort.hs:3:24-38] *Main&gt; :force as
1363 *** Exception: Prelude.undefined
1364 [-1: qsort.hs:3:24-38] *Main&gt; :print as
1365 as = 'b' : 'c' : (_t1::[Char])
1366 </screen>
1367
1368 <para>The exception itself is bound to a new variable,
1369 <literal>_exception</literal>.</para>
1370
1371 <para>Breaking on exceptions is particularly useful for finding out what
1372 your program was doing when it was in an infinite loop. Just hit
1373 Control-C, and examine the history to find out what was going
1374 on.</para>
1375 </sect2>
1376
1377 <sect2><title>Example: inspecting functions</title>
1378 <para>
1379 It is possible to use the debugger to examine function values.
1380 When we are at a breakpoint and a function is in scope, the debugger
1381 cannot show
1382 you the source code for it; however, it is possible to get some
1383 information by applying it to some arguments and observing the result.
1384 </para>
1385
1386 <para>
1387 The process is slightly complicated when the binding is polymorphic.
1388 We show the process by means of an example.
1389 To keep things simple, we will use the well known <literal>map</literal> function:
1390 <programlisting>
1391 import Prelude hiding (map)
1392
1393 map :: (a->b) -> a -> b
1394 map f [] = []
1395 map f (x:xs) = f x : map f xs
1396 </programlisting>
1397 </para>
1398
1399 <para>
1400 We set a breakpoint on <literal>map</literal>, and call it.
1401 <screen>
1402 *Main> :break 5
1403 Breakpoint 0 activated at map.hs:5:15-28
1404 *Main> map Just [1..5]
1405 Stopped at map.hs:(4,0)-(5,12)
1406 _result :: [b]
1407 x :: a
1408 f :: a -> b
1409 xs :: [a]
1410 </screen>
1411 GHCi tells us that, among other bindings, <literal>f</literal> is in scope.
1412 However, its type is not fully known yet,
1413 and thus it is not possible to apply it to any
1414 arguments. Nevertheless, observe that the type of its first argument is the
1415 same as the type of <literal>x</literal>, and its result type is shared
1416 with <literal>_result</literal>.
1417 </para>
1418
1419 <para>
1420 As we demonstrated earlier (<xref linkend="breakpoints" />), the
1421 debugger has some intelligence built-in to update the type of
1422 <literal>f</literal> whenever the types of <literal>x</literal> or
1423 <literal>_result</literal> are discovered. So what we do in this
1424 scenario is
1425 force <literal>x</literal> a bit, in order to recover both its type
1426 and the argument part of <literal>f</literal>.
1427 <screen>
1428 *Main> seq x ()
1429 *Main> :print x
1430 x = 1
1431 </screen>
1432 </para>
1433 <para>
1434 We can check now that as expected, the type of <literal>x</literal>
1435 has been reconstructed, and with it the
1436 type of <literal>f</literal> has been too:</para>
1437 <screen>
1438 *Main> :t x
1439 x :: Integer
1440 *Main> :t f
1441 f :: Integer -> b
1442 </screen>
1443 <para>
1444 From here, we can apply f to any argument of type Integer and observe
1445 the results.
1446 <screen><![CDATA[
1447 *Main> let b = f 10
1448 *Main> :t b
1449 b :: b
1450 *Main> b
1451 <interactive>:1:0:
1452 Ambiguous type variable `b' in the constraint:
1453 `Show b' arising from a use of `print' at <interactive>:1:0
1454 *Main> :p b
1455 b = (_t2::a)
1456 *Main> seq b ()
1457 ()
1458 *Main> :t b
1459 b :: a
1460 *Main> :p b
1461 b = Just 10
1462 *Main> :t b
1463 b :: Maybe Integer
1464 *Main> :t f
1465 f :: Integer -> Maybe Integer
1466 *Main> f 20
1467 Just 20
1468 *Main> map f [1..5]
1469 [Just 1, Just 2, Just 3, Just 4, Just 5]
1470 ]]></screen>
1471 In the first application of <literal>f</literal>, we had to do
1472 some more type reconstruction
1473 in order to recover the result type of <literal>f</literal>.
1474 But after that, we are free to use
1475 <literal>f</literal> normally.
1476 </para>
1477 </sect2>
1478
1479 <sect2><title>Limitations</title>
1480 <itemizedlist>
1481 <listitem>
1482 <para>When stopped at a breakpoint, if you try to evaluate a variable
1483 that is already under evaluation, the second evaluation will hang.
1484 The reason is
1485 that GHC knows the variable is under evaluation, so the new
1486 evaluation just waits for the result before continuing, but of
1487 course this isn't going to happen because the first evaluation is
1488 stopped at a breakpoint. Control-C can interrupt the hung
1489 evaluation and return to the prompt.</para>
1490 <para>The most common way this can happen is when you're evaluating a
1491 CAF (e.g. main), stop at a breakpoint, and ask for the value of the
1492 CAF at the prompt again.</para>
1493 </listitem>
1494 <listitem><para>
1495 Implicit parameters (see <xref linkend="implicit-parameters"/>) are only available
1496 at the scope of a breakpoint if there is an explicit type signature.
1497 </para>
1498 </listitem>
1499 </itemizedlist>
1500 </sect2>
1501 </sect1>
1502
1503 <sect1 id="ghci-invocation">
1504 <title>Invoking GHCi</title>
1505 <indexterm><primary>invoking</primary><secondary>GHCi</secondary></indexterm>
1506 <indexterm><primary><option>&ndash;&ndash;interactive</option></primary></indexterm>
1507
1508 <para>GHCi is invoked with the command <literal>ghci</literal> or
1509 <literal>ghc &ndash;&ndash;interactive</literal>. One or more modules or
1510 filenames can also be specified on the command line; this
1511 instructs GHCi to load the specified modules or filenames (and all
1512 the modules they depend on), just as if you had said
1513 <literal>:load <replaceable>modules</replaceable></literal> at the
1514 GHCi prompt (see <xref linkend="ghci-commands" />). For example, to
1515 start GHCi and load the program whose topmost module is in the
1516 file <literal>Main.hs</literal>, we could say:</para>
1517
1518 <screen>
1519 $ ghci Main.hs
1520 </screen>
1521
1522 <para>Most of the command-line options accepted by GHC (see <xref
1523 linkend="using-ghc"/>) also make sense in interactive mode. The ones
1524 that don't make sense are mostly obvious.</para>
1525
1526 <sect2>
1527 <title>Packages</title>
1528 <indexterm><primary>packages</primary><secondary>with GHCi</secondary></indexterm>
1529
1530 <para>Most packages (see <xref linkend="using-packages"/>) are
1531 available without needing to specify any extra flags at all:
1532 they will be automatically loaded the first time they are
1533 needed.</para>
1534
1535 <para>For hidden packages, however, you need to request the
1536 package be loaded by using the <literal>-package</literal> flag:</para>
1537
1538 <screen>
1539 $ ghci -package readline
1540 GHCi, version 6.8.1: http://www.haskell.org/ghc/ :? for help
1541 Loading package base ... linking ... done.
1542 Loading package readline-1.0 ... linking ... done.
1543 Prelude>
1544 </screen>
1545
1546 <para>The following command works to load new packages into a
1547 running GHCi:</para>
1548
1549 <screen>
1550 Prelude> :set -package <replaceable>name</replaceable>
1551 </screen>
1552
1553 <para>But note that doing this will cause all currently loaded
1554 modules to be unloaded, and you'll be dumped back into the
1555 <literal>Prelude</literal>.</para>
1556 </sect2>
1557
1558 <sect2>
1559 <title>Extra libraries</title>
1560 <indexterm><primary>libraries</primary><secondary>with GHCi</secondary></indexterm>
1561
1562 <para>Extra libraries may be specified on the command line using
1563 the normal <literal>-l<replaceable>lib</replaceable></literal>
1564 option. (The term <emphasis>library</emphasis> here refers to
1565 libraries of foreign object code; for using libraries of Haskell
1566 source code, see <xref linkend="ghci-modules-filenames"/>.) For
1567 example, to load the &ldquo;m&rdquo; library:</para>
1568
1569 <screen>
1570 $ ghci -lm
1571 </screen>
1572
1573 <para>On systems with <literal>.so</literal>-style shared
1574 libraries, the actual library loaded will the
1575 <filename>lib<replaceable>lib</replaceable>.so</filename>. GHCi
1576 searches the following places for libraries, in this order:</para>
1577
1578 <itemizedlist>
1579 <listitem>
1580 <para>Paths specified using the
1581 <literal>-L<replaceable>path</replaceable></literal>
1582 command-line option,</para>
1583 </listitem>
1584 <listitem>
1585 <para>the standard library search path for your system,
1586 which on some systems may be overridden by setting the
1587 <literal>LD_LIBRARY_PATH</literal> environment
1588 variable.</para>
1589 </listitem>
1590 </itemizedlist>
1591
1592 <para>On systems with <literal>.dll</literal>-style shared
1593 libraries, the actual library loaded will be
1594 <filename><replaceable>lib</replaceable>.dll</filename>. Again,
1595 GHCi will signal an error if it can't find the library.</para>
1596
1597 <para>GHCi can also load plain object files
1598 (<literal>.o</literal> or <literal>.obj</literal> depending on
1599 your platform) from the command-line. Just add the name the
1600 object file to the command line.</para>
1601
1602 <para>Ordering of <option>-l</option> options matters: a library
1603 should be mentioned <emphasis>before</emphasis> the libraries it
1604 depends on (see <xref linkend="options-linker"/>).</para>
1605 </sect2>
1606
1607 </sect1>
1608
1609 <sect1 id="ghci-commands">
1610 <title>GHCi commands</title>
1611
1612 <para>GHCi commands all begin with
1613 &lsquo;<literal>:</literal>&rsquo; and consist of a single command
1614 name followed by zero or more parameters. The command name may be
1615 abbreviated, with ambiguities being resolved in favour of the more
1616 commonly used commands.</para>
1617
1618 <variablelist>
1619 <varlistentry>
1620 <term>
1621 <literal>:abandon</literal>
1622 <indexterm><primary><literal>:abandon</literal></primary></indexterm>
1623 </term>
1624 <listitem>
1625 <para>Abandons the current evaluation (only available when stopped at
1626 a breakpoint).</para>
1627 </listitem>
1628 </varlistentry>
1629
1630 <varlistentry>
1631 <term>
1632 <literal>:add</literal> <replaceable>module</replaceable> ...
1633 <indexterm><primary><literal>:add</literal></primary></indexterm>
1634 </term>
1635 <listitem>
1636 <para>Add <replaceable>module</replaceable>(s) to the
1637 current <firstterm>target set</firstterm>, and perform a
1638 reload.</para>
1639 </listitem>
1640 </varlistentry>
1641
1642 <varlistentry>
1643 <term>
1644 <literal>:back</literal>
1645 <indexterm><primary><literal>:back</literal></primary></indexterm>
1646 </term>
1647 <listitem>
1648 <para>Travel back one step in the history. See <xref
1649 linkend="tracing" />. See also:
1650 <literal>:trace</literal>, <literal>:history</literal>,
1651 <literal>:forward</literal>.</para>
1652 </listitem>
1653 </varlistentry>
1654
1655 <varlistentry>
1656 <term>
1657 <literal>:break [<replaceable>identifier</replaceable> |
1658 [<replaceable>module</replaceable>] <replaceable>line</replaceable>
1659 [<replaceable>column</replaceable>]]</literal>
1660 </term>
1661 <indexterm><primary><literal>:break</literal></primary></indexterm>
1662 <listitem>
1663 <para>Set a breakpoint on the specified function or line and
1664 column. See <xref linkend="setting-breakpoints" />.</para>
1665 </listitem>
1666 </varlistentry>
1667
1668 <varlistentry>
1669 <term>
1670 <literal>:browse</literal> <optional><literal>*</literal></optional><replaceable>module</replaceable> ...
1671 <indexterm><primary><literal>:browse</literal></primary></indexterm>
1672 </term>
1673 <listitem>
1674 <para>Displays the identifiers defined by the module
1675 <replaceable>module</replaceable>, which must be either
1676 loaded into GHCi or be a member of a package. If the
1677 <literal>*</literal> symbol is placed before the module
1678 name, then <emphasis>all</emphasis> the identifiers defined
1679 in <replaceable>module</replaceable> are shown; otherwise
1680 the list is limited to the exports of
1681 <replaceable>module</replaceable>. The
1682 <literal>*</literal>-form is only available for modules
1683 which are interpreted; for compiled modules (including
1684 modules from packages) only the non-<literal>*</literal>
1685 form of <literal>:browse</literal> is available.</para>
1686 </listitem>
1687 </varlistentry>
1688
1689 <varlistentry>
1690 <term>
1691 <literal>:cd</literal> <replaceable>dir</replaceable>
1692 <indexterm><primary><literal>:cd</literal></primary></indexterm>
1693 </term>
1694 <listitem>
1695 <para>Changes the current working directory to
1696 <replaceable>dir</replaceable>. A
1697 &lsquo;<literal>&tilde;</literal>&rsquo; symbol at the
1698 beginning of <replaceable>dir</replaceable> will be replaced
1699 by the contents of the environment variable
1700 <literal>HOME</literal>.</para>
1701
1702 <para>NOTE: changing directories causes all currently loaded
1703 modules to be unloaded. This is because the search path is
1704 usually expressed using relative directories, and changing
1705 the search path in the middle of a session is not
1706 supported.</para>
1707 </listitem>
1708 </varlistentry>
1709
1710 <varlistentry>
1711 <term>
1712 <literal>:cmd</literal> <replaceable>expr</replaceable>
1713 <indexterm><primary><literal>:cmd</literal></primary></indexterm>
1714 </term>
1715 <listitem>
1716 <para>Executes <replaceable>expr</replaceable> as a computation of
1717 type <literal>IO String</literal>, and then executes the resulting
1718 string as a list of GHCi commands. Multiple commands are separated
1719 by newlines. The <literal>:cmd</literal> command is useful with
1720 <literal>:def</literal> and <literal>:set stop</literal>.</para>
1721 </listitem>
1722 </varlistentry>
1723
1724 <varlistentry>
1725 <term>
1726 <literal>:continue</literal>
1727 <indexterm><primary><literal>:continue</literal></primary></indexterm>
1728 </term>
1729 <listitem><para>Continue the current evaluation, when stopped at a
1730 breakpoint.</para>
1731 </listitem>
1732 </varlistentry>
1733
1734 <varlistentry>
1735 <term>
1736 <literal>:ctags</literal> <optional><replaceable>filename</replaceable></optional>
1737 <literal>:etags</literal> <optional><replaceable>filename</replaceable></optional>
1738 <indexterm><primary><literal>:etags</literal></primary>
1739 </indexterm>
1740 <indexterm><primary><literal>:etags</literal></primary>
1741 </indexterm>
1742 </term>
1743 <listitem>
1744 <para>Generates a &ldquo;tags&rdquo; file for Vi-style editors
1745 (<literal>:ctags</literal>) or
1746 Emacs-style editors (<literal>:etags</literal>). If
1747 no filename is specified, the defaulit <filename>tags</filename> or
1748 <filename>TAGS</filename> is
1749 used, respectively. Tags for all the functions, constructors and
1750 types in the currently loaded modules are created. All modules must
1751 be interpreted for these commands to work.</para>
1752 <para>See also <xref linkend="hasktags" />.</para>
1753 </listitem>
1754 </varlistentry>
1755
1756 <varlistentry>
1757 <term>
1758 <literal>:def</literal> <replaceable>name</replaceable> <replaceable>expr</replaceable>
1759 <indexterm><primary><literal>:def</literal></primary></indexterm>
1760 </term>
1761 <listitem>
1762 <para>The command <literal>:def</literal>
1763 <replaceable>name</replaceable>
1764 <replaceable>expr</replaceable> defines a new GHCi command
1765 <literal>:<replaceable>name</replaceable></literal>,
1766 implemented by the Haskell expression
1767 <replaceable>expr</replaceable>, which must have type
1768 <literal>String -> IO String</literal>. When
1769 <literal>:<replaceable>name</replaceable>
1770 <replaceable>args</replaceable></literal> is typed at the
1771 prompt, GHCi will run the expression
1772 <literal>(<replaceable>name</replaceable>
1773 <replaceable>args</replaceable>)</literal>, take the
1774 resulting <literal>String</literal>, and feed it back into
1775 GHCi as a new sequence of commands. Separate commands in
1776 the result must be separated by
1777 &lsquo;<literal>\n</literal>&rsquo;.</para>
1778
1779 <para>That's all a little confusing, so here's a few
1780 examples. To start with, here's a new GHCi command which
1781 doesn't take any arguments or produce any results, it just
1782 outputs the current date &amp; time:</para>
1783
1784 <screen>
1785 Prelude> let date _ = Time.getClockTime >>= print >> return ""
1786 Prelude> :def date date
1787 Prelude> :date
1788 Fri Mar 23 15:16:40 GMT 2001
1789 </screen>
1790
1791 <para>Here's an example of a command that takes an argument.
1792 It's a re-implementation of <literal>:cd</literal>:</para>
1793
1794 <screen>
1795 Prelude> let mycd d = Directory.setCurrentDirectory d >> return ""
1796 Prelude> :def mycd mycd
1797 Prelude> :mycd ..
1798 </screen>
1799
1800 <para>Or I could define a simple way to invoke
1801 &ldquo;<literal>ghc &ndash;&ndash;make Main</literal>&rdquo; in the
1802 current directory:</para>
1803
1804 <screen>
1805 Prelude> :def make (\_ -> return ":! ghc &ndash;&ndash;make Main")
1806 </screen>
1807
1808 <para>We can define a command that reads GHCi input from a
1809 file. This might be useful for creating a set of bindings
1810 that we want to repeatedly load into the GHCi session:</para>
1811
1812 <screen>
1813 Prelude> :def . readFile
1814 Prelude> :. cmds.ghci
1815 </screen>
1816
1817 <para>Notice that we named the command
1818 <literal>:.</literal>, by analogy with the
1819 &lsquo;<literal>.</literal>&rsquo; Unix shell command that
1820 does the same thing.</para>
1821 </listitem>
1822 </varlistentry>
1823
1824 <varlistentry>
1825 <term>
1826 <literal>:delete * | <replaceable>num</replaceable> ...</literal>
1827 <indexterm><primary><literal>:delete</literal></primary></indexterm>
1828 </term>
1829 <listitem>
1830 <para>Delete one or more breakpoints by number (use <literal>:show
1831 breaks</literal> to see the number of each breakpoint). The
1832 <literal>*</literal> form deletes all the breakpoints.</para>
1833 </listitem>
1834 </varlistentry>
1835
1836 <varlistentry>
1837 <term>
1838 <literal>:edit <optional><replaceable>file</replaceable></optional></literal>
1839 <indexterm><primary><literal>:edit</literal></primary></indexterm>
1840 </term>
1841 <listitem>
1842 <para>Opens an editor to edit the file
1843 <replaceable>file</replaceable>, or the most recently loaded
1844 module if <replaceable>file</replaceable> is omitted. The
1845 editor to invoke is taken from the <literal>EDITOR</literal>
1846 environment variable, or a default editor on your system if
1847 <literal>EDITOR</literal> is not set. You can change the
1848 editor using <literal>:set editor</literal>.</para>
1849 </listitem>
1850 </varlistentry>
1851
1852 <varlistentry>
1853 <term>
1854 <literal>:etags</literal>
1855 </term>
1856 <listitem>
1857 <para>See <literal>:ctags</literal>.</para>
1858 </listitem>
1859 </varlistentry>
1860
1861 <varlistentry>
1862 <term>
1863 <literal>:force <replaceable>identifier</replaceable> ...</literal>
1864 <indexterm><primary><literal>:force</literal></primary></indexterm>
1865 </term>
1866 <listitem>
1867 <para>Prints the value of <replaceable>identifier</replaceable> in
1868 the same way as <literal>:print</literal>. Unlike
1869 <literal>:print</literal>, <literal>:force</literal> evaluates each
1870 thunk that it encounters while traversing the value. This may
1871 cause exceptions or infinite loops, or further breakpoints (which
1872 are ignored, but displayed).</para>
1873 </listitem>
1874 </varlistentry>
1875
1876 <varlistentry>
1877 <term>
1878 <literal>:forward</literal>
1879 <indexterm><primary><literal>:forward</literal></primary></indexterm>
1880 </term>
1881 <listitem>
1882 <para>Move forward in the history. See <xref
1883 linkend="tracing" />. See also:
1884 <literal>:trace</literal>, <literal>:history</literal>,
1885 <literal>:back</literal>.</para>
1886 </listitem>
1887 </varlistentry>
1888
1889 <varlistentry>
1890 <term>
1891 <literal>:help</literal>
1892 <indexterm><primary><literal>:help</literal></primary></indexterm>
1893 </term>
1894 <term>
1895 <literal>:?</literal>
1896 <indexterm><primary><literal>:?</literal></primary></indexterm>
1897 </term>
1898 <listitem>
1899 <para>Displays a list of the available commands.</para>
1900 </listitem>
1901 </varlistentry>
1902
1903 <varlistentry>
1904 <term>
1905 <literal>:history [<replaceable>num</replaceable>]</literal>
1906 <indexterm><primary><literal>:history</literal></primary></indexterm>
1907 </term>
1908 <listitem>
1909 <para>Display the history of evaluation steps. With a number,
1910 displays that many steps (default: 20). For use with
1911 <literal>:trace</literal>; see <xref
1912 linkend="tracing" />.</para>
1913 </listitem>
1914 </varlistentry>
1915
1916 <varlistentry>
1917 <term>
1918 <literal>:info</literal> <replaceable>name</replaceable> ...
1919 <indexterm><primary><literal>:info</literal></primary></indexterm>
1920 </term>
1921 <listitem>
1922 <para>Displays information about the given name(s). For
1923 example, if <replaceable>name</replaceable> is a class, then
1924 the class methods and their types will be printed; if
1925 <replaceable>name</replaceable> is a type constructor, then
1926 its definition will be printed; if
1927 <replaceable>name</replaceable> is a function, then its type
1928 will be printed. If <replaceable>name</replaceable> has
1929 been loaded from a source file, then GHCi will also display
1930 the location of its definition in the source.</para>
1931 <para>For types and classes, GHCi also summarises instances that
1932 mention them. To avoid showing irrelevant information, an instance
1933 is shown only if (a) its head mentions <replaceable>name</replaceable>,
1934 and (b) all the other things mentioned in the instance
1935 are in scope (either qualified or otherwise) as a result of
1936 a <literal>:load</literal> or <literal>:module</literal> commands. </para>
1937 </listitem>
1938 </varlistentry>
1939
1940 <varlistentry>
1941 <term>
1942 <literal>:kind</literal> <replaceable>type</replaceable>
1943 <indexterm><primary><literal>:kind</literal></primary></indexterm>
1944 </term>
1945 <listitem>
1946 <para>Infers and prints the kind of
1947 <replaceable>type</replaceable>. The latter can be an arbitrary
1948 type expression, including a partial application of a type constructor,
1949 such as <literal>Either Int</literal>.</para>
1950 </listitem>
1951 </varlistentry>
1952
1953 <varlistentry>
1954 <term>
1955 <literal>:load</literal> <replaceable>module</replaceable> ...
1956 <indexterm><primary><literal>:load</literal></primary></indexterm>
1957 </term>
1958 <listitem>
1959 <para>Recursively loads the specified
1960 <replaceable>module</replaceable>s, and all the modules they
1961 depend on. Here, each <replaceable>module</replaceable>
1962 must be a module name or filename, but may not be the name
1963 of a module in a package.</para>
1964
1965 <para>All previously loaded modules, except package modules,
1966 are forgotten. The new set of modules is known as the
1967 <firstterm>target set</firstterm>. Note that
1968 <literal>:load</literal> can be used without any arguments
1969 to unload all the currently loaded modules and
1970 bindings.</para>
1971
1972 <para>After a <literal>:load</literal> command, the current
1973 context is set to:</para>
1974
1975 <itemizedlist>
1976 <listitem>
1977 <para><replaceable>module</replaceable>, if it was loaded
1978 successfully, or</para>
1979 </listitem>
1980 <listitem>
1981 <para>the most recently successfully loaded module, if
1982 any other modules were loaded as a result of the current
1983 <literal>:load</literal>, or</para>
1984 </listitem>
1985 <listitem>
1986 <para><literal>Prelude</literal> otherwise.</para>
1987 </listitem>
1988 </itemizedlist>
1989 </listitem>
1990 </varlistentry>
1991
1992 <varlistentry>
1993 <term>
1994 <literal>:main <replaceable>arg<subscript>1</subscript></replaceable> ... <replaceable>arg<subscript>n</subscript></replaceable></literal>
1995 <indexterm><primary><literal>:main</literal></primary></indexterm>
1996 </term>
1997 <listitem>
1998 <para>
1999 When a program is compiled and executed, it can use the
2000 <literal>getArgs</literal> function to access the
2001 command-line arguments.
2002 However, we cannot simply pass the arguments to the
2003 <literal>main</literal> function while we are testing in ghci,
2004 as the <literal>main</literal> function doesn't take its
2005 arguments directly.
2006 </para>
2007
2008 <para>
2009 Instead, we can use the <literal>:main</literal> command.
2010 This runs whatever <literal>main</literal> is in scope, with
2011 any arguments being treated the same as command-line arguments,
2012 e.g.:
2013 </para>
2014
2015 <screen>
2016 Prelude> let main = System.Environment.getArgs >>= print
2017 Prelude> :main foo bar
2018 ["foo","bar"]
2019 </screen>
2020
2021 </listitem>
2022 </varlistentry>
2023
2024 <varlistentry>
2025 <term>
2026 <literal>:module <optional>+|-</optional> <optional>*</optional><replaceable>mod<subscript>1</subscript></replaceable> ... <optional>*</optional><replaceable>mod<subscript>n</subscript></replaceable></literal>
2027 <indexterm><primary><literal>:module</literal></primary></indexterm>
2028 </term>
2029 <term>
2030 <literal>import <replaceable>mod</replaceable></literal>
2031 </term>
2032 <listitem>
2033 <para>Sets or modifies the current context for statements
2034 typed at the prompt. The form <literal>import
2035 <replaceable>mod</replaceable></literal> is equivalent to
2036 <literal>:module +<replaceable>mod</replaceable></literal>.
2037 See <xref linkend="ghci-scope"/> for
2038 more details.</para>
2039 </listitem>
2040 </varlistentry>
2041
2042 <varlistentry>
2043 <term>
2044 <literal>:print </literal> <replaceable>names</replaceable> ...
2045 <indexterm><primary><literal>:print</literal></primary></indexterm>
2046 </term>
2047 <listitem>
2048 <para>Prints a value without forcing its evaluation.
2049 <literal>:print</literal> may be used on values whose types are
2050 unknown or partially known, which might be the case for local
2051 variables with polymorphic types at a breakpoint. While inspecting
2052 the runtime value, <literal>:print</literal> attempts to
2053 reconstruct the type of the value, and will elaborate the type in
2054 GHCi's environment if possible. If any unevaluated components
2055 (thunks) are encountered, then <literal>:print</literal> binds
2056 a fresh variable with a name beginning with <literal>_t</literal>
2057 to each thunk. See <xref linkend="breakpoints" /> for more
2058 information. See also the <literal>:sprint</literal> command,
2059 which works like <literal>:print</literal> but does not bind new
2060 variables.</para>
2061 </listitem>
2062 </varlistentry>
2063
2064 <varlistentry>
2065 <term>
2066 <literal>:quit</literal>
2067 <indexterm><primary><literal>:quit</literal></primary></indexterm>
2068 </term>
2069 <listitem>
2070 <para>Quits GHCi. You can also quit by typing control-D
2071 at the prompt.</para>
2072 </listitem>
2073 </varlistentry>
2074
2075 <varlistentry>
2076 <term>
2077 <literal>:reload</literal>
2078 <indexterm><primary><literal>:reload</literal></primary></indexterm>
2079 </term>
2080 <listitem>
2081 <para>Attempts to reload the current target set (see
2082 <literal>:load</literal>) if any of the modules in the set,
2083 or any dependent module, has changed. Note that this may
2084 entail loading new modules, or dropping modules which are no
2085 longer indirectly required by the target.</para>
2086 </listitem>
2087 </varlistentry>
2088
2089 <varlistentry>
2090 <term>
2091 <literal>:set</literal> <optional><replaceable>option</replaceable>...</optional>
2092 <indexterm><primary><literal>:set</literal></primary></indexterm>
2093 </term>
2094 <listitem>
2095 <para>Sets various options. See <xref linkend="ghci-set"/>
2096 for a list of available options. The
2097 <literal>:set</literal> command by itself shows which
2098 options are currently set.</para>
2099 </listitem>
2100 </varlistentry>
2101
2102 <varlistentry>
2103 <term>
2104 <literal>:set</literal> <literal>args</literal> <replaceable>arg</replaceable> ...
2105 <indexterm><primary><literal>:set args</literal></primary></indexterm>
2106 </term>
2107 <listitem>
2108 <para>Sets the list of arguments which are returned when the
2109 program calls <literal>System.getArgs</literal><indexterm><primary>getArgs</primary>
2110 </indexterm>.</para>
2111 </listitem>
2112 </varlistentry>
2113
2114 <varlistentry>
2115 <term>
2116 <literal>:set</literal> <literal>editor</literal> <replaceable>cmd</replaceable>
2117 </term>
2118 <listitem>
2119 <para>Sets the command used by <literal>:edit</literal> to
2120 <replaceable>cmd</replaceable>.</para>
2121 </listitem>
2122 </varlistentry>
2123
2124 <varlistentry>
2125 <term>
2126 <literal>:set</literal> <literal>prog</literal> <replaceable>prog</replaceable>
2127 <indexterm><primary><literal>:set prog</literal></primary></indexterm>
2128 </term>
2129 <listitem>
2130 <para>Sets the string to be returned when the program calls
2131 <literal>System.getProgName</literal><indexterm><primary>getProgName</primary>
2132 </indexterm>.</para>
2133 </listitem>
2134 </varlistentry>
2135
2136 <varlistentry>
2137 <term>
2138 <literal>:set</literal> <literal>prompt</literal> <replaceable>prompt</replaceable>
2139 </term>
2140 <listitem>
2141 <para>Sets the string to be used as the prompt in GHCi.
2142 Inside <replaceable>prompt</replaceable>, the sequence
2143 <literal>%s</literal> is replaced by the names of the
2144 modules currently in scope, and <literal>%%</literal> is
2145 replaced by <literal>%</literal>.</para>
2146 </listitem>
2147 </varlistentry>
2148
2149 <varlistentry>
2150 <term>
2151 <literal>:set</literal> <literal>stop</literal>
2152 [<replaceable>num</replaceable>] <replaceable>cmd</replaceable>
2153 </term>
2154 <listitem>
2155 <para>Set a command to be executed when a breakpoint is hit, or a new
2156 item in the history is selected. The most common use of
2157 <literal>:set stop</literal> is to display the source code at the
2158 current location, e.g. <literal>:set stop :list</literal>.</para>
2159
2160 <para>If a number is given before the command, then the commands are
2161 run when the specified breakpoint (only) is hit. This can be quite
2162 useful: for example, <literal>:set stop 1 :continue</literal>
2163 effectively disables breakpoint 1, by running
2164 <literal>:continue</literal> whenever it is hit (although GHCi will
2165 still emit a message to say the breakpoint was hit). What's more,
2166 with cunning use of <literal>:def</literal> and
2167 <literal>:cmd</literal> you can use <literal>:set stop</literal> to
2168 implement conditional breakpoints:</para>
2169 <screen>
2170 *Main> :def cond \expr -> return (":cmd if (" ++ expr ++ ") then return \"\" else return \":continue\"")
2171 *Main> :set stop 0 :cond (x &lt; 3)
2172 </screen>
2173 <para>Ignoring breakpoints for a specified number of iterations is
2174 also possible using similar techniques.</para>
2175 </listitem>
2176 </varlistentry>
2177
2178 <varlistentry>
2179 <term>
2180 <literal>:show bindings</literal>
2181 <indexterm><primary><literal>:show bindings</literal></primary></indexterm>
2182 </term>
2183 <listitem>
2184 <para>Show the bindings made at the prompt and their
2185 types.</para>
2186 </listitem>
2187 </varlistentry>
2188
2189 <varlistentry>
2190 <term>
2191 <literal>:show breaks</literal>
2192 <indexterm><primary><literal>:show breaks</literal></primary></indexterm>
2193 </term>
2194 <listitem>
2195 <para>List the active breakpoints.</para>
2196 </listitem>
2197 </varlistentry>
2198
2199 <varlistentry>
2200 <term>
2201 <literal>:show context</literal>
2202 <indexterm><primary><literal>:show context</literal></primary></indexterm>
2203 </term>
2204 <listitem>
2205 <para>List the active evaluations that are stopped at breakpoints.</para>
2206 </listitem>
2207 </varlistentry>
2208
2209 <varlistentry>
2210 <term>
2211 <literal>:show modules</literal>
2212 <indexterm><primary><literal>:show modules</literal></primary></indexterm>
2213 </term>
2214 <listitem>
2215 <para>Show the list of modules currently loaded.</para>
2216 </listitem>
2217 </varlistentry>
2218
2219 <varlistentry>
2220 <term>
2221 <literal>:show [args|prog|prompt|editor|stop]</literal>
2222 <indexterm><primary><literal>:show</literal></primary></indexterm>
2223 </term>
2224 <listitem>
2225 <para>Displays the specified setting (see
2226 <literal>:set</literal>).</para>
2227 </listitem>
2228 </varlistentry>
2229
2230 <varlistentry>
2231 <term>
2232 <literal>:sprint</literal>
2233 <indexterm><primary><literal>:sprint</literal></primary></indexterm>
2234 </term>
2235 <listitem>
2236 <para>Prints a value without forcing its evaluation.
2237 <literal>:sprint</literal> is similar to <literal>:print</literal>,
2238 with the difference that unevaluated subterms are not bound to new
2239 variables, they are simply denoted by &lsquo;_&rsquo;.</para>
2240 </listitem>
2241 </varlistentry>
2242
2243 <varlistentry>
2244 <term>
2245 <literal>:step [<replaceable>expr</replaceable>]</literal>
2246 <indexterm><primary><literal>:step</literal></primary></indexterm>
2247 </term>
2248 <listitem>
2249 <para>Single-step from the last breakpoint. With an expression
2250 argument, begins evaluation of the expression with a
2251 single-step.</para>
2252 </listitem>
2253 </varlistentry>
2254
2255 <varlistentry>
2256 <term>
2257 <literal>:trace [<replaceable>expr</replaceable>]</literal>
2258 <indexterm><primary><literal>:trace</literal></primary></indexterm>
2259 </term>
2260 <listitem>
2261 <para>Evaluates the given expression (or from the last breakpoint if
2262 no expression is given), and additionally logs the evaluation
2263 steps for later inspection using <literal>:history</literal>. See
2264 <xref linkend="tracing" />.</para>
2265 </listitem>
2266 </varlistentry>
2267
2268 <varlistentry>
2269 <term>
2270 <literal>:type</literal> <replaceable>expression</replaceable>
2271 <indexterm><primary><literal>:type</literal></primary></indexterm>
2272 </term>
2273 <listitem>
2274 <para>Infers and prints the type of
2275 <replaceable>expression</replaceable>, including explicit
2276 forall quantifiers for polymorphic types. The monomorphism
2277 restriction is <emphasis>not</emphasis> applied to the
2278 expression during type inference.</para>
2279 </listitem>
2280 </varlistentry>
2281
2282 <varlistentry>
2283 <term>
2284 <literal>:undef</literal> <replaceable>name</replaceable>
2285 <indexterm><primary><literal>:undef</literal></primary></indexterm>
2286 </term>
2287 <listitem>
2288 <para>Undefines the user-defined command
2289 <replaceable>name</replaceable> (see <literal>:def</literal>
2290 above).</para>
2291 </listitem>
2292 </varlistentry>
2293
2294 <varlistentry>
2295 <term>
2296 <literal>:unset</literal> <replaceable>option</replaceable>...
2297 <indexterm><primary><literal>:unset</literal></primary></indexterm>
2298 </term>
2299 <listitem>
2300 <para>Unsets certain options. See <xref linkend="ghci-set"/>
2301 for a list of available options.</para>
2302 </listitem>
2303 </varlistentry>
2304
2305 <varlistentry>
2306 <term>
2307 <literal>:!</literal> <replaceable>command</replaceable>...
2308 <indexterm><primary><literal>:!</literal></primary></indexterm>
2309 <indexterm><primary>shell commands</primary><secondary>in GHCi</secondary></indexterm>
2310 </term>
2311 <listitem>
2312 <para>Executes the shell command
2313 <replaceable>command</replaceable>.</para>
2314 </listitem>
2315 </varlistentry>
2316
2317 </variablelist>
2318 </sect1>
2319
2320 <sect1 id="ghci-set">
2321 <title>The <literal>:set</literal> command</title>
2322 <indexterm><primary><literal>:set</literal></primary></indexterm>
2323
2324 <para>The <literal>:set</literal> command sets two types of
2325 options: GHCi options, which begin with
2326 &lsquo;<literal>+</literal>&rsquo;, and &ldquo;command-line&rdquo;
2327 options, which begin with &lsquo;-&rsquo;. </para>
2328
2329 <para>NOTE: at the moment, the <literal>:set</literal> command
2330 doesn't support any kind of quoting in its arguments: quotes will
2331 not be removed and cannot be used to group words together. For
2332 example, <literal>:set -DFOO='BAR BAZ'</literal> will not do what
2333 you expect.</para>
2334
2335 <sect2>
2336 <title>GHCi options</title>
2337 <indexterm><primary>options</primary><secondary>GHCi</secondary>
2338 </indexterm>
2339
2340 <para>GHCi options may be set using <literal>:set</literal> and
2341 unset using <literal>:unset</literal>.</para>
2342
2343 <para>The available GHCi options are:</para>
2344
2345 <variablelist>
2346 <varlistentry>
2347 <term>
2348 <literal>+r</literal>
2349 <indexterm><primary><literal>+r</literal></primary></indexterm>
2350 <indexterm><primary>CAFs</primary><secondary>in GHCi</secondary></indexterm>
2351 <indexterm><primary>Constant Applicative Form</primary><see>CAFs</see></indexterm>
2352 </term>
2353 <listitem>
2354 <para>Normally, any evaluation of top-level expressions
2355 (otherwise known as CAFs or Constant Applicative Forms) in
2356 loaded modules is retained between evaluations. Turning
2357 on <literal>+r</literal> causes all evaluation of
2358 top-level expressions to be discarded after each
2359 evaluation (they are still retained
2360 <emphasis>during</emphasis> a single evaluation).</para>
2361
2362 <para>This option may help if the evaluated top-level
2363 expressions are consuming large amounts of space, or if
2364 you need repeatable performance measurements.</para>
2365 </listitem>
2366 </varlistentry>
2367
2368 <varlistentry>
2369 <term>
2370 <literal>+s</literal>
2371 <indexterm><primary><literal>+s</literal></primary></indexterm>
2372 </term>
2373 <listitem>
2374 <para>Display some stats after evaluating each expression,
2375 including the elapsed time and number of bytes allocated.
2376 NOTE: the allocation figure is only accurate to the size
2377 of the storage manager's allocation area, because it is
2378 calculated at every GC. Hence, you might see values of
2379 zero if no GC has occurred.</para>
2380 </listitem>
2381 </varlistentry>
2382
2383 <varlistentry>
2384 <term>
2385 <literal>+t</literal>
2386 <indexterm><primary><literal>+t</literal></primary></indexterm>
2387 </term>
2388 <listitem>
2389 <para>Display the type of each variable bound after a
2390 statement is entered at the prompt. If the statement is a
2391 single expression, then the only variable binding will be
2392 for the variable
2393 &lsquo;<literal>it</literal>&rsquo;.</para>
2394 </listitem>
2395 </varlistentry>
2396 </variablelist>
2397 </sect2>
2398
2399 <sect2 id="ghci-cmd-line-options">
2400 <title>Setting GHC command-line options in GHCi</title>
2401
2402 <para>Normal GHC command-line options may also be set using
2403 <literal>:set</literal>. For example, to turn on
2404 <option>-fglasgow-exts</option>, you would say:</para>
2405
2406 <screen>
2407 Prelude> :set -fglasgow-exts
2408 </screen>
2409
2410 <para>Any GHC command-line option that is designated as
2411 <firstterm>dynamic</firstterm> (see the table in <xref
2412 linkend="flag-reference"/>), may be set using
2413 <literal>:set</literal>. To unset an option, you can set the
2414 reverse option:</para>
2415 <indexterm><primary>dynamic</primary><secondary>options</secondary></indexterm>
2416
2417 <screen>
2418 Prelude> :set -fno-glasgow-exts
2419 </screen>
2420
2421 <para><xref linkend="flag-reference"/> lists the reverse for each
2422 option where applicable.</para>
2423
2424 <para>Certain static options (<option>-package</option>,
2425 <option>-I</option>, <option>-i</option>, and
2426 <option>-l</option> in particular) will also work, but some may
2427 not take effect until the next reload.</para>
2428 <indexterm><primary>static</primary><secondary>options</secondary></indexterm>
2429 </sect2>
2430 </sect1>
2431 <sect1 id="ghci-dot-files">
2432 <title>The <filename>.ghci</filename> file</title>
2433 <indexterm><primary><filename>.ghci</filename></primary><secondary>file</secondary>
2434 </indexterm>
2435 <indexterm><primary>startup</primary><secondary>files, GHCi</secondary>
2436 </indexterm>
2437
2438 <para>When it starts, unless the <literal>-ignore-dot-ghci</literal>
2439 flag is given, GHCi reads and executes commands from
2440 <filename>./.ghci</filename>, followed by
2441 <filename>$HOME/.ghci</filename>.</para>
2442
2443 <para>The <filename>.ghci</filename> in your home directory is
2444 most useful for turning on favourite options (eg. <literal>:set
2445 +s</literal>), and defining useful macros. Placing a
2446 <filename>.ghci</filename> file in a directory with a Haskell
2447 project is a useful way to set certain project-wide options so you
2448 don't have to type them everytime you start GHCi: eg. if your
2449 project uses GHC extensions and CPP, and has source files in three
2450 subdirectories A, B and C, you might put the following lines in
2451 <filename>.ghci</filename>:</para>
2452
2453 <screen>
2454 :set -fglasgow-exts -cpp
2455 :set -iA:B:C
2456 </screen>
2457
2458 <para>(Note that strictly speaking the <option>-i</option> flag is
2459 a static one, but in fact it works to set it using
2460 <literal>:set</literal> like this. The changes won't take effect
2461 until the next <literal>:load</literal>, though.)</para>
2462
2463 <para>Two command-line options control whether the
2464 <filename>.ghci</filename> files are read:</para>
2465
2466 <variablelist>
2467 <varlistentry>
2468 <term>
2469 <option>-ignore-dot-ghci</option>
2470 <indexterm><primary><option>-ignore-dot-ghci</option></primary></indexterm>
2471 </term>
2472 <listitem>
2473 <para>Don't read either <filename>./.ghci</filename> or
2474 <filename>$HOME/.ghci</filename> when starting up.</para>
2475 </listitem>
2476 </varlistentry>
2477 <varlistentry>
2478 <term>
2479 <option>-read-dot-ghci</option>
2480 <indexterm><primary><option>-read-dot-ghci</option></primary></indexterm>
2481 </term>
2482 <listitem>
2483 <para>Read <filename>.ghci</filename> and
2484 <filename>$HOME/.ghci</filename>. This is normally the
2485 default, but the <option>-read-dot-ghci</option> option may
2486 be used to override a previous
2487 <option>-ignore-dot-ghci</option> option.</para>
2488 </listitem>
2489 </varlistentry>
2490 </variablelist>
2491
2492 </sect1>
2493
2494 <sect1 id="ghci-obj">
2495 <title>Compiling to object code inside GHCi</title>
2496
2497 <para>By default, GHCi compiles Haskell source code into byte-code
2498 that is interpreted by the runtime system. GHCi can also compile
2499 Haskell code to object code: to turn on this feature, use the
2500 <option>-fobject-code</option> flag either on the command line or
2501 with <literal>:set</literal> (the option
2502 <option>-fbyte-code</option> restores byte-code compilation
2503 again). Compiling to object code takes longer, but typically the
2504 code will execute 10-20 times faster than byte-code.</para>
2505
2506 <para>Compiling to object code inside GHCi is particularly useful
2507 if you are developing a compiled application, because the
2508 <literal>:reload</literal> command typically runs much faster than
2509 restarting GHC with <option>--make</option> from the command-line,
2510 because all the interface files are already cached in
2511 memory.</para>
2512
2513 <para>There are disadvantages to compiling to object-code: you
2514 can't set breakpoints in object-code modules, for example. Only
2515 the exports of an object-code module will be visible in GHCi,
2516 rather than all top-level bindings as in interpreted
2517 modules.</para>
2518 </sect1>
2519
2520 <sect1 id="ghci-faq">
2521 <title>FAQ and Things To Watch Out For</title>
2522
2523 <variablelist>
2524 <varlistentry>
2525 <term>The interpreter can't load modules with foreign export
2526 declarations!</term>
2527 <listitem>
2528 <para>Unfortunately not. We haven't implemented it yet.
2529 Please compile any offending modules by hand before loading
2530 them into GHCi.</para>
2531 </listitem>
2532 </varlistentry>
2533
2534 <varlistentry>
2535 <term>
2536 <literal>-O</literal> doesn't work with GHCi!
2537 <indexterm><primary><option>-O</option></primary></indexterm>
2538 </term>
2539 <listitem>
2540 <para>For technical reasons, the bytecode compiler doesn't
2541 interact well with one of the optimisation passes, so we
2542 have disabled optimisation when using the interpreter. This
2543 isn't a great loss: you'll get a much bigger win by
2544 compiling the bits of your code that need to go fast, rather
2545 than interpreting them with optimisation turned on.</para>
2546 </listitem>
2547 </varlistentry>
2548
2549 <varlistentry>
2550 <term>Unboxed tuples don't work with GHCi</term>
2551 <listitem>
2552 <para>That's right. You can always compile a module that
2553 uses unboxed tuples and load it into GHCi, however.
2554 (Incidentally the previous point, namely that
2555 <literal>-O</literal> is incompatible with GHCi, is because
2556 the bytecode compiler can't deal with unboxed
2557 tuples).</para>
2558 </listitem>
2559 </varlistentry>
2560
2561 <varlistentry>
2562 <term>Concurrent threads don't carry on running when GHCi is
2563 waiting for input.</term>
2564 <listitem>
2565 <para>This should work, as long as your GHCi was built with
2566 the <option>-threaded</option> switch, which is the default.
2567 Consult whoever supplied your GHCi installation.</para>
2568 </listitem>
2569 </varlistentry>
2570
2571 <varlistentry>
2572 <term>After using <literal>getContents</literal>, I can't use
2573 <literal>stdin</literal> again until I do
2574 <literal>:load</literal> or <literal>:reload</literal>.</term>
2575
2576 <listitem>
2577 <para>This is the defined behaviour of
2578 <literal>getContents</literal>: it puts the stdin Handle in
2579 a state known as <firstterm>semi-closed</firstterm>, wherein
2580 any further I/O operations on it are forbidden. Because I/O
2581 state is retained between computations, the semi-closed
2582 state persists until the next <literal>:load</literal> or
2583 <literal>:reload</literal> command.</para>
2584
2585 <para>You can make <literal>stdin</literal> reset itself
2586 after every evaluation by giving GHCi the command
2587 <literal>:set +r</literal>. This works because
2588 <literal>stdin</literal> is just a top-level expression that
2589 can be reverted to its unevaluated state in the same way as
2590 any other top-level expression (CAF).</para>
2591 </listitem>
2592 </varlistentry>
2593
2594 <varlistentry>
2595 <term>I can't use Control-C to interrupt computations in
2596 GHCi on Windows.</term>
2597 <listitem>
2598 <para>See <xref linkend="ghci-windows"/>.</para>
2599 </listitem>
2600 </varlistentry>
2601
2602 <varlistentry>
2603 <term>The default buffering mode is different in GHCi to GHC.</term>
2604 <listitem>
2605 <para>
2606 In GHC, the stdout handle is line-buffered by default.
2607 However, in GHCi we turn off the buffering on stdout,
2608 because this is normally what you want in an interpreter:
2609 output appears as it is generated.
2610 </para>
2611 </listitem>
2612 </varlistentry>
2613 </variablelist>
2614 </sect1>
2615
2616 </chapter>
2617
2618 <!-- Emacs stuff:
2619 ;;; Local Variables: ***
2620 ;;; mode: xml ***
2621 ;;; sgml-parent-document: ("users_guide.xml" "book" "chapter") ***
2622 ;;; End: ***
2623 -->