Thread

1. jjmarr · 1789514348 · focus · HN ↗

   Open the C++ example up and the first thing I see:

   ```cpp std::cout << "Received ReportCoordinateFrameSettings" << std::endl; ```

   Generally, I've heard `std::endl` instead of \n has bad performance because it forces the statement to print immediately. And because cout is guaranteed to flush anyways when the program ends, you're adding a delay for no reason.

   I wonder if there's something I'm not seeing that led to them adopting this rule. e.g. "abnormal program termination" caused by the weapon blowing itself up circumventing a buffer flush?

   1. __d · 1789516169 · focus · HN ↗

      For a long time, std::endl demonstrated that you were a proper C++ programmer, not some neckbeard C apologist. It wasn’t until C++ had „won“ that it became acceptable to use \n again.

Unofficial Hacker News client; not affiliated with Y Combinator.