[EMAIL PROTECTED] writes:
> Christian Sievers <[EMAIL PROTECTED]> writes:
> > I noticed two things which I think might be called bugs, at least I am
> > near doing so:
> >
> > The first thing really annoys me:
> > If you input something like
> >
> > [0,x] where x=x
> >
> > you get no output at all before you interupt.
> > I think the output is buffered, and I don't like it.
>
> You're right - that is annoying.
> A simple fix is to change the value of "FLUSH_EVERY" in prelude.h
> and recompile:
>
> 99c99
> < #define FLUSHEVERY (DJGPP2)
> ---
> > #define FLUSHEVERY 1
>
> This affects the behaviour of primPutStr and primHPutStr.
>
> I'm putting this fix into the next release - people should shout if
> they think this is a bad idea.
>
Hmm..if you want to disable buffering on stdout, why not use Haskell
for the job - performing
hSetBuffering stdout NoBuffering
in the read-eval-print loop before doing anything else..will this
not have the desired effect? There's one caveat though, the IO
interface provided by Hugs (v. 970410 at least) does not export the
set&get ops on Handle buffering.
If you want to make this default for stdout, turn off buffering during
initialisation - flushing after every string output (on every kind of
Handle) sounds a bit excessive to me (if that's the interpretation of
FLUSHEVERY).
Just a thought.
--Sigbjorn
