News for hackers. Stuff that matters.
Re:How to write to stderr so people will like you by CamperBob on Friday April 16, 2010 @05:25PM (#1271977)
I'm in the habit of using doing a setbuf(stdout,NULL) in the beginning of all my console apps, anyway. Buffered console I/O is something that made sense 20 years ago but certainly not anymore.

If you did a setbuf(stderr,NULL) as well as setbuf(stdout,NULL), you'd achieve the same effect that the author's going for, with no need to remember to flush.

Re:How to write to stderr so people will like you by nitrogen on Saturday April 17, 2010 @12:01AM (#1272591)
It really depends on how much data you need to write to stdout. If you're writing a single character at a time with no buffering, many terminal programs (GNOME terminal, etc.) will struggle to put out more than a few dozen lines per second, which can significantly slow down your program (I've known people who redirect their cc's stdout to /dev/null to avoid terminal latency slowing the build).