Repository : ssh://darcs.haskell.org//srv/darcs/ghc On branch : ghc-7.2
http://hackage.haskell.org/trac/ghc/changeset/bb262abd55326938596997fe79f1b4b2326a26ef >--------------------------------------------------------------- commit bb262abd55326938596997fe79f1b4b2326a26ef Author: Austin Seipp <[email protected]> Date: Mon Jul 4 13:21:40 2011 -0500 Typo >--------------------------------------------------------------- docs/users_guide/extending_ghc.xml | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/docs/users_guide/extending_ghc.xml b/docs/users_guide/extending_ghc.xml index ec771c5..11cd75d 100644 --- a/docs/users_guide/extending_ghc.xml +++ b/docs/users_guide/extending_ghc.xml @@ -85,7 +85,7 @@ data Foo = ... <sect1 id="ghc-as-a-library"> <title>Using GHC as a Library</title> - <para>The <literal>ghc</literal> package exposes most of GHC's frontend to users, and thus allows you to write programs that leverage it. This library is actually the same library used by GHC's internal, frontend compilation driver, and thus allows you to write tools that programatically compile source code and inspect it. Such functionality is useful in order to write things like IDE or refactoring tools. As a simple example, here's a program which compiles a module, much like ghc itself does by default when invoked:</para> + <para>The <literal>ghc</literal> package exposes most of GHC's frontend to users, and thus allows you to write programs that leverage it. This library is actually the same library used by GHC's internal, frontend compilation driver, and thus allows you to write tools that programmatically compile source code and inspect it. Such functionality is useful in order to write things like IDE or refactoring tools. As a simple example, here's a program which compiles a module, much like ghc itself does by default when invoked:</para> <programlisting> import GHC _______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
