Changes between Initial Version and Version 1 of Ticket #27383, comment 1


Ignore:
Timestamp:
02/28/19 10:06:30 (10 months ago)
Author:
jdemeyer
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #27383, comment 1

    initial v1  
    33I would argue that eclib should actually flush whenever it's "done" producing output. Note that `<< endl` flushes the output, so this is probably a matter of replacing some `<< "\n"` by `<< endl` in eclib, in particular in `mw::process()`. Alternatively, you could add an explicit `cout.flush()`.
    44
    5 For eclib, I guess that I/O performance is not an issue (you aren't producing megabytes of output per second, right?). So then there is little reason to ''not'' use `<< endl`.
     5Note that flushing too often can degrade performance. But I guess that I/O performance is not an issue for eclib (you aren't producing megabytes of output per second, right?). So then there is little reason to ''not'' use `<< endl`.