3 ms·
> I don't buy this at all. Stroustrup was keen on this... Buy it or don't, it remains 100% fact. You may abandon fact, but at the cost of remaining credibility
by ncmncm 5y ago
> I don't buy this at all. Stroustrup was keen on this...
Buy it or don't, it remains 100% fact. You may abandon fact, but at the cost of remaining credibility.
Where constrained to be backward compatible with C, as C++ was, there is no choice but to implement both increment operators. Period.
You may insist he could have avoided implementing overloading for increment operators. But then, generic code would not work. Crippling the language to conform to your personal preference would have killed its future, and we would be discussing neither C++ nor Rust, which depends utterly on C++ for most of its design. Furthermore, I daresay you had no such preference at the time, and probably could not have expressed it if you had.
Smugness about good luck is a great personal failing.
- tialaramex 5y ago> Buy it or don't, it remains 100% fact. That's not how facts work. It's a fact that C++ does have these operators, it is not a fact that this was unavoidable. And remember Swift removed these operators. Earlier versions of Swift had them, current ones don't, they were a bad idea and they're gone now. That's a thing a serious language did, not a toy language used by six PhD students, a real practical language with a population of working programmers. > Where constrained to be backward compatible with C, as C++ was ie: conditionally. C++ chooses to be somewhat compatible, but not compatible enough that medium-sized C codebases work unaltered or that larger ones can reliably be converted at all. Which shouldn't be a huge surprise as its own "compatibility" story from C++ 98 onward is likewise a trail of misery and despair. > Furthermore, I daresay you had no such preference at the time In 1982 when Stroustrup named the language C++ and thus sealed this particular deal, no probably not. I believe I did not even purchase a macro assembler (my first way to write programs that weren't in either raw machine code or Basic) until slightly after that date. And I have no doubt that insufferable teenage me thought the pair of increment operators was a great idea when he got a primitive C++ compiler (having never had a C compiler before that) some years later, his poetry and protocol design were both awful too, we certainly shouldn't put him in charge of designing a modern programming language.
- ncmncm 5y agoYou have said something deeply stupid, and when called on it, doubled down. So, I will just leave it there.