On 19-01-2014 19:59, Christopher Wellons wrote:
When the shell is set to interactive (i.e. "-interactive"), the output
(stdout) is flushed with every prompt (shell.c:422) but stderr is not.
Stderr is suppose to be unbuffered so that flushing is not required. Or is
that different for windows?
According to the stderr Linux man page stderr is unbuffered, which would
be why I'm not having a problem in Linux:
The stream stderr is unbuffered. The stream stdout is line-buffered
when it points to a terminal.
I'm unable to find any documentation about this for Windows, but since
I'm seeing stderr buffering it must not be unbuffered in Windows.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Is this not biting you?
It is acceptable—and normal—for standard output and standard error to be
directed to the same destination, such as the text terminal. Messages
appear in the same order as the program writes them, unless buffering is
involved. (For example, a common situation is when the standard error
stream is unbuffered but the standard output stream is line-buffered; in
this case, text written to standard error later may appear on the
terminal earlier, if the standard output stream's buffer is not yet full.)
source:
http://en.wikipedia.org/wiki/Standard_streams#Standard_error_.28stderr.29
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
