- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
You must log in or register to comment.
print('string\n', end='')I just learned that in Python, it’s fucking terrible. Python is a fucking mess and my next script will be in a different language.
As a python lover, I have to ask, what don’t you like about it and what languages do you generally prefer?
Perhaps TS is not a terrible language for shell scripts after all
Never tried it, but I will probably be more at home than python.
python is a bad joke that never ends
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
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!";
Simple.
\nwhen you just want a newline.
printlnwhen you need to flush at the moment.Useful in case you are printing a debug output right before some function that might do bed stuff to buffers.
I only program in C. I was under the assumption that \n also flushes
It depends on whether you are printing to a terminal or to a file (and yes the terminal is also a file), and even then you can control the flushing behaviour using something like
unbufferI remember having to
fflusha couple of times.
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
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.
I prefer \n for 0.001% better performance
deleted by creator
I prefer endl for more typing because it lets me pretend to work more than I am
^ least deranged coder
Kinda in Java, you can call System.out.println or you can call System.out.print and explicitly write the newline.
I haven’t looked at the code but I always assumed that
printlnwas a call toprintwith a new line added to the original input.
Something like this:void print(String text) { ... } void println(String text) { this.print(text + '\n'); }That is pretty much what it does except it doesn’t hardcode
\nbut instead uses the proper line ending for the platform it’s running on.
\n is fun until you’re an a system that needs an additional \r
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.
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?
std::cout << "\nwhy not both" << std::endl;C++ style text streams are bad and a dead-end design and
'\n'.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.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.It’s a “stream manipulator” function that not only generates a new line, it also flushes the stream.
fprintf(stdout, "%c", '\012');Doesn’t endl predate C++?
It’s not in C, if that’s what you mean.
