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.
python is a bad joke that never ends
As a python lover, I have to ask, what don’t you like about it and what languages do you generally prefer?
I prefer strongly typed languages. Using bytes isn’t intuitive.
Transforming certain data types into other data types is often not straightforward.
The identation is the worst though. Let me format the code however I want.
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.
Doesn’t endl predate C++?
It’s not in C, if that’s what you mean.
No debate, std::endl can be a disaster on some platforms due to flushing crap all the time.
Considering std::cout should only directly be used when you are too lazy to place breakpoints, I totally get the decision to auto-flush.
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.
I hear C++ was greatly inspired by the fifth circle of hell.
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!
Just because the box says something is flushable doesn’t mean you should flush it.
\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.
C++ style text streams are bad and a dead-end design and
'\n'.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.I haven’t worked with java for a couple of months now, currently working in Delphi, so could not remember the how else to do new line except backslash n on top of my head. :-)
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.
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!
Just
puts(“I’m a teapot”);:)printfis superior and more concise, andsnprintfis practically the only C string manipulation function that is not painful to use.Try to print a 32-bit unsigned int as hexadecimal number of exactly 8 digits, using
cout. You can dostd::hexandstd::setw(8)andstd::setfill('0')and don’t forget to usestd::decafterwards, or you can just, you know,printf("%08x")like a sane person.Just don’t forget to use
-Werror=formatbut that is the default option on many compilers today.C++23 now includes
std::printwhich is exactly likeprintfbut better, so the whole argument is over.I went digging in cppref at the format library bc I thought c++20 or c++23 added something cool.
Found
std::printand was about to reply to this comment to share it bc I thought it was interesting. Then I read the last sentence.Darn you and your predicting my every move /j
As long as it doesn’t end in ;
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!";
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
deleted by creator
fprintf(stdout, "%c", '\012');
