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.
Yeah it's an artificial dichotomy based on a popular misconception of what std::endl is and how \n is interpreted.
Ultimately it does not ask about line endings, but about flushing, which is a completely orthogonal question.
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.
\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
Don’t most terminals flush the buffer on newline anyway?
It is the stream itself that is buffered, so the terminal does not handle the contents until the stream is flushed.
Maybe, but there is the internal buffer. Also, most I/O happens in files not consoles
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.
God bless your soul.
#define endl "\n"
Environment.NewLine()
/* I'm new to this language so just imagine there is a new line here when it prints: */
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.
Environment.NewLine might exist in C#
It might do. I encountered it last week as I needed it for a powershell script. So it exists in that at least
\r\n
Rebel side \0
vbCrLf
Endl is faster to type