Mail Archives: djgpp/2001/05/16/10:30:14
Hans-Bernhard Broeker wrote:
> Michiel de Bondt <michielb AT sci DOT kun DOT nl> wrote:
> > Hello,
>
> > I did not found this question in the FAQ. I use cprintf some times
> > and then I use printf. But a few times, the printf is done at an old
> > cursor position, i.e. the cursor is there somewhere in the middle of
> > the cprintfs. The cprintfs are not affected, i.e. they are not done
> > from the position after the printf, but from the right position.
>
> > So I wish to know the console variant of fflush (stdout) for standard
> > output.
>
> There is none --- cprintf() isn't buffered, so it doesn't need any
> fflush workalike, to begin with. Instead, you'ld have to be sure you
> fflush(stdout) before any cprintf() or gotoxy() call following a
> printf().
>
This does not agree with observation. Probably, Windows 95 should be
blamed.
>
> The basic problem is that you simply should not mix cprintf() and normal
> printf(), like that. There's no good reason to do so, anyway. If you're
> going to use cprintf(), use it for all output.
>
I wish to print all information to stdout, except the progress asterisks
"*" and search
paths, and the "\b \b" to remove them. The program dvips distinguishes
console output and
standard output as well, i.e. it seems so at least. How can that be? Or
does the program
have undetermined behavior if you do not redirect stdout?
>
> --
> Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
> Even if all the snow were burnt, ashes would remain.
- Raw text -