Skip to content

Make sure that logging an error should first makes sure that the cout is flushed #6

@ClarkMcGrew

Description

@ClarkMcGrew

Logging goes to std::cout and errors got to std::cerr (that is as it should be). During non-interactive running, output is buffered so that std::cout and std::cerr output is out of sequence. Since errors mark fixed points in the code where something is going wrong, they should make sure that cout is flushed before making the error output.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions