Repository : ssh://darcs.haskell.org//srv/darcs/ghc

On branch  : master

http://hackage.haskell.org/trac/ghc/changeset/1c5e89eda88dc79061ec885ccf21eed55c7d7440

>---------------------------------------------------------------

commit 1c5e89eda88dc79061ec885ccf21eed55c7d7440
Author: Daniel Fischer <[email protected]>
Date:   Mon May 30 11:16:15 2011 +0200

    glasgow_exts.xml whitespace

>---------------------------------------------------------------

 docs/users_guide/glasgow_exts.xml |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/docs/users_guide/glasgow_exts.xml 
b/docs/users_guide/glasgow_exts.xml
index 2490855..f44bf79 100644
--- a/docs/users_guide/glasgow_exts.xml
+++ b/docs/users_guide/glasgow_exts.xml
@@ -427,7 +427,7 @@ Indeed, the bindings can even be recursive.
 
       <para>The hash sign does not change semantics at all.  We tend to use 
variable
        names ending in "&num;" for unboxed values or types (e.g. 
<literal>Int&num;</literal>),
-       but there is no requirement to do so; they are just plain ordinary 
variables.
+        but there is no requirement to do so; they are just plain ordinary 
variables.
        Nor does the <option>-XMagicHash</option> extension bring anything into 
scope.
        For example, to bring <literal>Int&num;</literal> into scope you must
        import <literal>GHC.Prim</literal> (see <xref linkend="primitives"/>);



_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc

Reply via email to