projects
/
ghc-base.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (from parent 1:
f3eeca6
)
[project @ 2002-09-14 09:27:21 by panne]
author
panne
<unknown>
Sat, 14 Sep 2002 09:27:21 +0000
(09:27 +0000)
committer
panne
<unknown>
Sat, 14 Sep 2002 09:27:21 +0000
(09:27 +0000)
Make Haddock happy
GHC/IOBase.lhs
patch
|
blob
|
history
diff --git
a/GHC/IOBase.lhs
b/GHC/IOBase.lhs
index
60ae45b
..
6f7d9c9
100644
(file)
--- a/
GHC/IOBase.lhs
+++ b/
GHC/IOBase.lhs
@@
-133,9
+133,10
@@
performs side effects, then the relative order in which those side
effects take place (relative to the main I\/O trunk, or other calls to
'unsafePerformIO') is indeterminate. You have to be careful when
writing and compiling modules that use 'unsafePerformIO':
effects take place (relative to the main I\/O trunk, or other calls to
'unsafePerformIO') is indeterminate. You have to be careful when
writing and compiling modules that use 'unsafePerformIO':
- * Use @{-# NOINLINE foo #-}@ as a pragma on any function @foo@
+
+ * Use @{\-\# NOINLINE foo \#-\}@ as a pragma on any function @foo@
that calls 'unsafePerformIO'. If the call is inlined,
that calls 'unsafePerformIO'. If the call is inlined,
- the I/O may be performed more than once.
+ the I\/O may be performed more than once.
* Use the compiler flag @-fno-cse@ to prevent common sub-expression
elimination being performed on the module, which might combine
* Use the compiler flag @-fno-cse@ to prevent common sub-expression
elimination being performed on the module, which might combine