From d5ab53493d661acc52e2d693258076136e634e95 Mon Sep 17 00:00:00 2001 From: simonmar Date: Thu, 28 Jun 2001 11:34:42 +0000 Subject: [PATCH] [project @ 2001-06-28 11:34:42 by simonmar] ghci may take multiple modules on the command line. --- ghc/docs/users_guide/ghci.sgml | 19 ++++++++----------- 1 file changed, 8 insertions(+), 11 deletions(-) diff --git a/ghc/docs/users_guide/ghci.sgml b/ghc/docs/users_guide/ghci.sgml index 1e3bee5..5fc8d9f 100644 --- a/ghc/docs/users_guide/ghci.sgml +++ b/ghc/docs/users_guide/ghci.sgml @@ -521,22 +521,19 @@ Wed Mar 14 12:23:13 GMT 2001 GHCi is invoked with the command ghci or - ghc --interactive. A module or filename can - also be specified on the command line; this instructs GHCi to load - the that module or filename (and all the modules it depends on), - just as if you had said :load - module at the GHCi prompt - (see ). For example, to start GHCi - and load the program whose topmost module is in the file - Main.hs, we could say: + ghc --interactive. One or more modules or + filenames can also be specified on the command line; this + instructs GHCi to load the specified modules or filenames (and all + the modules they depend on), just as if you had said + :load modules at the + GHCi prompt (see ). For example, to + start GHCi and load the program whose topmost module is in the + file Main.hs, we could say: $ ghci Main.hs - Note: only one module name or filename - may be given on the command line. - Most of the command-line options accepted by GHC (see ) also make sense in interactive mode. The ones that don't make sense are mostly obvious; for example, GHCi -- 1.7.10.4