Alternative to cout logging in Windows Environment.

[lucky6969b]

I find out that Java println and many fold faster than cout in C++.
I am currently using cout as a quick visual logging tool.
I wonder how I can make the same lightning fast text output in C++?
Thanks
Jack

[GCDEF]

https://msdn.microsoft.com/en-us/library/dhxsse89.aspx

[lucky6969b]

How can I output to a separate standalone console pane just for debugging instead of interweaving other debug outputs to the same pane?
Thanks
Jack

[Igor Vartanov]

What I usually prefer is using plain text logging to disk file (lightning fast ) along with a tool that autodetects file update and dispalys the file tail (in my case it's always FAR Manager viewer). The most beatiful thing about this approach is that the log remains available for offline analysis, e.g. grepping.

Oh, one more thing: I never use cout, but always do use printf. Lightning fast

[2kaud]

Oh, one more thing: I never use cout, but always do use printf. Lightning fast

It has been shown in these forums previously that i/o using the c library functions is faster than using the c++ i/o streams (for MS).

[OReubens]

things like this Always end up being about programmer convenience vs performance.

if speed is really your concern. Then low level file IO with your own formatting is going to beat the pants out of anything.

C FILE io offers buffered and formatted IO at a cost.

C++ io offers buffered, formatted, and typed IO (and easy changing to other stream types) at an even larger cost.

Part of the problem of cout in particular is that output is constantly being flushed, which negates part of buffering features.
file stream io can be made faster by increasing the internal buffer.

[Arjay]

Why not use a logging library that allows you to configure the outputs (log to file, log to console, log to the debugger, log to the event viewer (windows), etc.)?