Frederik Eaton wrote:
Hey, it looks like the output of two threads is being interleaved one
character at a time. Is that really the most efficient way to schedule
threads? Anyway, so I guess I need to set stdout and stderr to be line
buffered? Perhaps that should be the default setting? ...
#873: Add System.Directory.installFile
---+
Reporter: simonmar|Owner:
Type: task| Status: new
Priority: normal |Milestone: 6.6
#798: Ix{Int}.index: Index (402849792) out of range ((0,100))
-+--
Reporter: [EMAIL PROTECTED] | Owner:
Type: bug | Status: closed
Priority: normal
#852: Browsing a module in ghci can cause a panic
--+-
Reporter: mnislaih | Owner:
Type: bug | Status: closed
Priority: normal |
#874: SEGFAULT in stg_ap_ppp_info()
---+
Reporter: guest |Owner:
Type: bug | Status: new
Priority: normal |Milestone: 6.4.2
Component:
#874: SEGFAULT in stg_ap_ppp_info()
-+--
Reporter: guest | Owner:
Type: bug | Status: new
Priority: normal | Milestone: 6.4.2
Component: Runtime
#875: assert fails on HEAD
-+--
Reporter: guest |Owner:
Type: bug | Status: new
Priority: normal|Milestone:
Component: Compiler |
Do you think that the standard GHC behavior should be for
multithreaded programs to produce garbage on stderr?
C is different because it's not lazy. Usually small lines are printed
to stderr; they fit in a single 'write' call and even if there are
multiple such calls they usually happen within
