projects
/
ghc-hetmet.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
[project @ 2000-04-07 15:24:15 by simonpj]
[ghc-hetmet.git]
/
ghc
/
docs
/
users_guide
/
using.sgml
diff --git
a/ghc/docs/users_guide/using.sgml
b/ghc/docs/users_guide/using.sgml
index
4358ac8
..
595e13d
100644
(file)
--- a/
ghc/docs/users_guide/using.sgml
+++ b/
ghc/docs/users_guide/using.sgml
@@
-991,7
+991,12
@@
sight!
<Para>
GHC <Emphasis>only</Emphasis> keeps detailed dependency information
<Para>
GHC <Emphasis>only</Emphasis> keeps detailed dependency information
-for “user” modules, not for “library” modules.
+for “user” modules, not for “Prelude” modules.
+It distinguishes Prelude modules because their names start with
+"Prel", so don't start your modules that way!
+
+<!-- April 2000: hack disabled. Now we use a different hack!
+
It distinguishes the two by a hack: a module whose
<Filename>.hi</Filename> file has an absolute path name is considered
a library module, while a relative path name indicates a user module.
It distinguishes the two by a hack: a module whose
<Filename>.hi</Filename> file has an absolute path name is considered
a library module, while a relative path name indicates a user module.
@@
-1010,6
+1015,7
@@
A path is considered “absolute” if it starts with
“<Filename>B:/</Filename>”,
“<Filename>B:\</Filename>” etc).
</Para>
“<Filename>B:/</Filename>”,
“<Filename>B:\</Filename>” etc).
</Para>
+-->
<Para>
Patrick Sansom had a workshop paper about how all this is done (though
<Para>
Patrick Sansom had a workshop paper about how all this is done (though