According to syntax postfix increment returns copy of unmodified variable (C++ == C), while prefix increment returns incremented variable (++C == C + 1).
+C+
Have you ever tried sugar, or…
Only the syntactic kind
Cpp
++C would make the language totally irrelevant in alphanumeric listings of languages
After simply managing a point of sale system for a retail chain, I hate you for even suggesting this./s It is almost as bad as all the insane ideas about date notation. The only correct notation is YYYY/MM/DD.
ISO 8601 is good for computers, but as a human i prefer DD/MM/YYYY, which is more convenient for everyday use. USA format is abomination though.
We read numbers big->small. YYYY>MM>DD
But when you wanna figure out what day it is, usually the month doesn’t change. I love ISO 8601 as much for programming and sorting as much as the next person, but for close dates for humans, DMY is still pretty good.
As a human ISO8601 is great. Ambiguity is far far worse, than having to read out a date aloud in an order any other than the order it is habitually spoken.
No it’s not. Only care about the date in month? Just say the date. Do you care about the month too? Month Day is your answer. Do you care about the full date? Add on the year
Saying it out loud and using a worded date in this order is what I mean. English simply does not support “Twenty Twenty-four September Twenty” or “2024 September 20”.
Sorry for the late response. Written and spoken order can be different (ie. $2 is pronounced two dollars and not dollar two)
2024-09-20 can be wordy:
In the year of 2024, in the 9th month, on the 20th day.
Yeah, $2 can also be transliterated, whereupon it becomes “two dollars”; 2024-09-20 can also be transliterated, wherein there are two major competing orders: DMY and MDY. And I agree that other major orders are too wordy, and that’s sort of my point.
Many people are ahead used to the DD.MM.YYYY format. They are also already totally ok with the hh:mm:ss format so apparently there’s no problem ascending or descending order. Inconsistency really bothers me, so we should just pick one and stick with it. Preferably the ISO style, if you ask me.
wtf, it’s YYYY-MM-DD brother
Why not invent even more notations? We did YYYY.MM.DD at work.
Just please don’t do yyyyMMdd with each field being optional and possibly one or two characters.
I personally do YYYY.MM.DD for all of my personal filing. Sue me.
Edit: personally, of course.
But it’s still C
I think ++C is going full ahead to D
Agreed. C is a char, and
++'C'results in'D'.
PHP should stand for “Pre Hypertext Processor”.
Instead of being a recursive acronym for “PHP: Hypertext Preprocessor”.
GNU’s Not Unix
First there was C
Then C+, and no one gave a shit, so they made C++
It’s just C with stuff added to it twice.
Then what about C++++, aka C#.
double-plus-good
???
If c = 1, then c++ = 2
#include <iostream> using namespace std;
int main() {
int i = 10;
cout << i++ << endl;
cout << i << endl;
}
postfix ++ increments the variable.
Postfix increments variable too, but as a side effect. in your code
cout << i++ << endl;prints 10 which means, that i++ returned copy of unincremented i.Yes c++ == c. That’s the point Bjarne Stroustrup made. It is the C language but then it’s better.
Nowadays they’re not completely compatible. But originally it was a preprocessor that created the C equivalent to be compiled. You could write C++ that compiled with a C compiler as long as you didn’t use the extra features.
Yeah.
Perhaps ++C == Java or something.
I’m sure that’s offensive to some, so apologies for airing the thought.
4 decades too late with this. You’re not the first.
i give it a c-
The fediverse really is filled with programmers… that nearly looks like math but the type I learned at school.
