QTextStream input and output executing in wrong order

[jrmrjnck]

Okay, so the buffering type explanation makes sense. I guess that different distributions might have different defaults for in/out/err, which are set in some other location (the kernel? libc?). Stderr on my system exhibited the same behavior as stdout (line buffering).

I also found you can flush the stream with a manipulator, as in

out << "Answer: " << flush;

out << "Answer: " << flush;

To copy to clipboard, switch view to plain text mode 

which kind of takes care of my concern about writing too much code to do a simple thing.

[Zlatomir]

Your problem doesn't have anything to do with stdout (buffered) or stderr(not buffered).

Your issue is with the QTextStream which is buffered. The flush in the code that i wrote is flushing the QTextStream buffer (not the stdout, your QTextStream has only the same name as std::cout, that is one reason i said you should use different names )

[jrmrjnck]

So, please correct me if I'm wrong, but there is no way then to make QTextStream unbuffered, and the only way to reliably output to the console is to write a newline or flush the buffer. It seems true that the text is being held up at QTextStream as you state, since both QTextStream and iostream wrap the same stdout file handle, while iostream "works" for me.

That takes care of my problem, but I still wonder what would cause the same code to execute differently on different computers, and even change how it executes on the same system over time?