this post was submitted on 17 Oct 2024
1368 points (98.9% liked)

RetroGaming

19795 readers
439 users here now

Vintage gaming community.

Rules:

  1. Be kind.
  2. No spam or soliciting for money.
  3. No racism or other bigotry allowed.
  4. Obviously nothing illegal.

If you see these please report them.

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] BigDanishGuy@sh.itjust.works 7 points 2 months ago (1 children)

Well ackshually <<std::endl is not the preferred way to do it according to the C++ Core Guidelines https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rio-endl

So to be a good little lemming I've added a \n, but I refuse to flush!

Interesting... today I learned. But since I only ever use std::cout in my debugging code (i.e. DURING debugging) or for status outputs of the application (for small apps), and for everything else I use my own logging framework that uses printf & syslog udp messages... luckily nothing I need to refactor :D