Post funny things about programming here! (Or just rant about your favourite programming language.)
If I'm writing C++, I'm usually optimizing for portability over performance, in which case I would prefer std::endl as it would yield the best results regardless of platform; it also keeps the end-of-line character out of other strings, making code just a little cleaner.
\n is for when I'm done pretending that anything that isn't Unix-like is OK, or I'm counting the cycles of every branch instruction.
std::endl provides zero portability benefits. C++ does have a portable newline abstraction, but it is called \n, not endl.
Thank you two for demonstrating the image in the post so well.
No, there's no guarantee that in every context \n is translated portably.
The same is true of std::endl. std::endl is simply defined as << '\n' << std::flush; nothing more, nothing less. In all cases where endl gives you a "properly translated" newline, so does \n.
Ahhh, I see. Looks like the magic happens somewhere further down in iostream.
It's controlled by whether the stream's opened in text mode or binary mode. On Unix, they're the same, but on Windows, text mode has line ending conversion.
They aren't the same thing so the comparison is weird.
endl has a flush which is important when doing something like embedded work or RTOS development. If i was doing multiple lines they all were \n until the last line when i actually want to push the buffer.
Obviously depending on the tuning of the compiler's optimization multiple flushes could be reduced but the goal should always be to write as optimal as possible.
but the goal should always be to write as optimal as possible.
Within reason.
Over optimization is a curse on getting done.
Who in the hell is using iostreams in an RTOS
Sometimes you work in a codebase that was decided on by others for reasons you don't know.
Several. Probably dozens
\n, because I ordered a newline, not a flush.
What the heck is endl???
std::endl is used in output streams in C++ to end the line, using the os specific line termination sequence, and flush the buffer.
The later one is a performance issue in many cases, why the use of "\n" is considered preferred
Instead of this:
std::cout << "Hello world.\n";
You can do this:
std::cout << "Hello world." << endl;
The fact that you used the namespace for cout but not for endl inordinately bothers me
Boy am I glad I don’t do C++ anymore. That string handling with the overloaded bitshift operator was wild.
From memory it's a way to declare a line ending after your string.
#define endl "\n"
Environment.NewLine()
/* I'm new to this language so just imagine there is a new line here when it prints: */
\r\n gang
Are you a modem by any chance?
No, I'm a teapot
Get out
Yeah \r gang4lyfe
os.linesep
Lol jk none of my stuff runs on Windows anyway
I'm on side \PHP_EOL
I like that you added the absolute namespace identifier or whatever its called
I don't always namespace but when I do I fully qualify.
\r\n
Environment.NewLine might exist in C#
Microsoft really creating the problem and then forcing you to use their solution.
It might do. I encountered it last week as I needed it for a powershell script. So it exists in that at least
Rebel side \0
vbCrLf
Endl is faster to type