Malcolm Wallace wrote:
Simon Marlow 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, plea
Simon Marlow 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 submit a bug re
Brandon S. Allbery KF8NH wrote:
On 2009 Feb 20, at 4:38, Serge D. Mechveliani wrote:
The first command outputs
-
t = ((a : nil) + (b : nil))
Bug:
substitute {(X, a), (Xs, nil), (Ys, (b : nil))} X:
sort mismatch in substitution
---
On 2009 Feb 20, at 4:38, Serge D. Mechveliani wrote:
The first command outputs
-
t = ((a : nil) + (b : nil))
Bug:
substitute {(X, a), (Xs, nil), (Ys, (b : nil))} X:
sort mismatch in substitution
-
And the second command sk
I'm just guessing, but it looks like a buffering problem.
When a program dies an abnormal death (like the "Bug:" thing probably
is) then the stdout buffer is not flushed and you'll miss that bit of
the output.
You could set stdout in NoBuffering mode and see if that helps.
-- Lennart
On Fri, Fe
People,
I observe the output difference in running ./Bug
and ./Bug >& log
(under Linux) for the program
import Dumatel
main = do calcInput <- readFile "List0.inp"
(putStr $ parseComputeShow calcInput)
where
parseComputeShow calcInpu
