projects
/
ghc-hetmet.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
In user guide, don't claim that ghci never generates .hi files
[ghc-hetmet.git]
/
docs
/
users_guide
/
ghci.xml
diff --git
a/docs/users_guide/ghci.xml
b/docs/users_guide/ghci.xml
index
8e7dda0
..
0409400
100644
(file)
--- a/
docs/users_guide/ghci.xml
+++ b/
docs/users_guide/ghci.xml
@@
-1080,7
+1080,7
@@
right :: [a]
<title>Listing and deleting breakpoints</title>
<para>The list of breakpoints currently enabled can be displayed using
<title>Listing and deleting breakpoints</title>
<para>The list of breakpoints currently enabled can be displayed using
- <literal>:show breaks</literal></para>:
+ <literal>:show breaks</literal>:</para>
<screen>
*Main> :show breaks
[0] Main qsort.hs:1:11-12
<screen>
*Main> :show breaks
[0] Main qsort.hs:1:11-12
@@
-1488,7
+1488,7
@@
Just 20
</listitem>
<listitem><para>
Implicit parameters (see <xref linkend="implicit-parameters"/>) are only available
</listitem>
<listitem><para>
Implicit parameters (see <xref linkend="implicit-parameters"/>) are only available
- at the scope of a breakpoint if there is a explicit type signature.
+ at the scope of a breakpoint if there is an explicit type signature.
</para>
</listitem>
</itemizedlist>
</para>
</listitem>
</itemizedlist>
@@
-1516,9
+1516,7
@@
$ ghci Main.hs
<para>Most of the command-line options accepted by GHC (see <xref
linkend="using-ghc"/>) also make sense in interactive mode. The ones
<para>Most of the command-line options accepted by GHC (see <xref
linkend="using-ghc"/>) also make sense in interactive mode. The ones
- that don't make sense are mostly obvious; for example, GHCi
- doesn't generate interface files, so options related to interface
- file generation won't have any effect.</para>
+ that don't make sense are mostly obvious.</para>
<sect2>
<title>Packages</title>
<sect2>
<title>Packages</title>