Simon Marlow marlo...@gmail.com wrote:
stdout should be flushed when the program exits, regardless of whether
it exits as a result of a clean exit or an exception. I've just
checked the code, and that's certainly what is supposed to happen.
If anyone has evidence to the contrary, please
Malcolm Wallace wrote:
Simon Marlow marlo...@gmail.com wrote:
stdout should be flushed when the program exits, regardless of whether
it exits as a result of a clean exit or an exception. I've just
checked the code, and that's certainly what is supposed to happen.
If anyone has evidence to
-
And the second command skips (in ./log) the line of t = ...
Who can tell what is the matter?
The ghc runtime doesn't flush stdout when an exception stops the
program. This is arguably a bug in the runtime; if you set stdout to
line buffering or no buffering you should get pretty
-
t = ((a : nil) + (b : nil))
Bug:
substitute {(X, a), (Xs, nil), (Ys, (b : nil))} X:
sort mismatch in substitution
-
And the second command skips (in ./log) the line of t = ...
Who can tell what is the matter?
How to have identic outputs
skips (in ./log) the line of t = ...
Who can tell what is the matter?
The ghc runtime doesn't flush stdout when an exception stops the
program. This is arguably a bug in the runtime; if you set stdout to
line buffering or no buffering you should get pretty much the same
output from both
