- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
You must log in or register to comment.
Just
puts(“I’m a teapot”);:)Maybe c# has similar. There’s \r\n or \n like c++ and Environment.NewLine.
Probably it’s similar in that Environment.NewLine takes into account the operating system in use and I wonder if endl in c++ does the same thing?
C# also has verbatim strings, in which you can just put a literal newline.
string foo = @"This string has a line break!";
No debate, std::endl can be a disaster on some platforms due to flushing crap all the time.
It’s a very C++ thing that the language developers saw the clusterfuck that is stream flushing on the kernel and decided that the right course of action was to create another fucking layer of hidden inconsistent flushing.
programmers manage to do stupid shit in every language. i was wondering if there was a way to stop them, and golang comes close but maybe proves it can’t be done. idk!
I hear C++ was greatly inspired by the fifth circle of hell.
Just because the box says something is flushable doesn’t mean you should flush it.
Considering std::cout should only directly be used when you are too lazy to place breakpoints, I totally get the decision to auto-flush.
\n is fun until you’re an a system that needs an additional \r
Bedeviled NXP/ARM SDK stdlib. Hate it, we need \n\r there. Why!!! What a PITA.
Unix needed only \n because it had complex drivers that could replace \n with whatever sequence of special characters the printer needed. Also, while carriage return is useful, they saw little use for line feed
On dos (which was intended for less powerful hardware than unix) you had to actually use the correct sequence which often but not always was \r\n (because teleprinters used that and because it’s the “most correct” one).
Now that teleprinters don’t exist, and complex drivers are not an issue for windows, and everyone prefers to have a single \n, windows still uses \r\n, for backward compatibility.
If
endlis a function call and/or macro that magically knows the right line ending for whatever ultimately stores or reads the output stream, then, ugly though it is,endlis the right thing to use.If a language or compiler automatically “do(es) the right thing” with
\nas well, then check your local style guide. Is this your code? Do what you will. Is this for your company? Better to check what’s acceptable.If you want to guarantee a Unix line ending use
\012instead. Or\cJif your language is sufficiently warped.It’s a “stream manipulator” function that not only generates a new line, it also flushes the stream.
Ah don’t worry, if you do
fopen(file, "w")on Windows and forget to use"wb"flag, it will automatically replace all your\nwith\r\nwhen you dofwrite, then you will try to debug for half a day your corrupted jpeg file, which totally never happened to me because I’m an experienced C++ developer who can never make such a novice mistake.
Fuck endl, all my homies hate endl
bloods 4 lyfe
Cout << “\n”; is dumb and you should feel bad
You’re right, that is incredibly dumb. Just not for the reasons you think it is. Imagine using iostream rather than stdio and unironically trying to clown on \n
Is this not a debate for freshman students and other assorted opinionated know-nothings? Or just people shitposting.
My mistake. You think it’s srs.
(And your opinion is still bad)
Oh no! Did I hurt your feelings by clapping back when you insulted me on a shitpost comment chain? Your lack of self awareness is astounding
Feel this is relevant https://www.youtube.com/watch?v=IkpZggx4yNI
Doesn’t endl predate C++?
It’s not in C, if that’s what you mean.
As long as it doesn’t end in ;
fprintf(stdout, "%c", '\012');Wasn’t this {fmt} library merged into STL now? Does this solve this issue?
Anyways, there was also a constant that is the OS line ending without a flush, right?
C++ style text streams are bad and a dead-end design and
'\n'.deleted by creator
std::cout << "\nwhy not both" << std::endl;In PHP it exists as well. I try to use PHP_EOL but when I’m lazy I simply do “\n”.
For me the answer is “Building backend applications with it instead of CLI applications, like Lerdorf intended.”
But also
"\n"because it’s easier andPHP_EOLis just an alias for"\n"; it’s not even platform-dependent.PHP_EOL depends on your host system, it’s
\r\non Windows.I don’t really want to use what Lerdorf intended, PHP <= 4 was horrible, 5.x was mainly getting slowly rid of nonsense and with 7.x PHP started its slow path of redemption and entered its modern era.
While Lerdorf’s vision was great at that time for its intended use case, I wouldn’t want to build anything serious in it.
It actually outputs
"\n"on a Windows system, but modern Windows to recognise that as enough of a newline, nowadays.I don’t really want to use what Lerdorf intended, PHP <= 4 was horrible
Actually a great point!
I am very sorry to remind everyone about the existence of Visual Basic, but it has:
- VbCrLf
- VbNewLine
- ControlChars.CrLf
- ControlChars.NewLine
- Environment.NewLine
- Chr(13) & Chr(10)
And I know what you’re asking: Yes, of course all of them have subtly different behavior, and some of them only work in VB.NET and not in classic VB or VBA.
The only thing you can rely on is that “\r\n” doesn’t work.
Apology not accepted, fuck you for reminding me!
great reminder to avoid microsoft products as much as i can
