I was listening to a google talk by Andrei Alexandrescu on the D programming language when he threw out a one liner about the "endl" fiasco. I just thought endl was the preferred way to signify the end of a line and flush the buffer for a stream. Why is it considered a fiasco? Should I not be using it in my code?
相关问题
- Sorting 3 numbers without branching [closed]
- How to compile C++ code in GDB?
- Why does const allow implicit conversion of refere
- thread_local variables initialization
- What uses more memory in c++? An 2 ints or 2 funct
相关文章
- Class layout in C++: Why are members sometimes ord
- How to mock methods return object with deleted cop
- Which is the best way to multiply a large and spar
- C++ default constructor does not initialize pointe
- Selecting only the first few characters in a strin
- What exactly do pointers store? (C++)
- Converting glm::lookat matrix to quaternion and ba
- What is the correct way to declare and use a FILE
Reposting from my comment:
(I assume) He just means that many, especially new, C++ programmers use
std::endl
blindly instead of'\n'
for newline, flushing unnecessarily frequently and potentially making the performance of their program abysmal.I.e., most people are taught that
std::endl
is the canonical way to insert a newline into a stream even though it is very rarely necessary or appropriate to flush it.It is some people's opinion (*cough*) that
std::endl
shouldn't even be in the standard, as it is so rarely appropriate and not a significant typing savings over'\n' << std::flush
anyway.TL;DR(s):
std::endl
buys you nothing except usually worse performance and usually more typing.