- In C "getchar" returns... an int.
- Pointers and array are kinda the same thing, but not exactly. The rules for when an array decays into a pointer are sometimes unintuitive and surprising.
- Same thing for the implicit integer types promotions.
- `char *s = "foo"` is not at all the same thing as `char s[] = "foo"`. Arguably the former should be considered erroneous, but compiles just fine in C. G++ gives a warning for the same code however.
- There's also the ridiculous "gets" function that's so poorly designed it could be part of PHP. This one finally got officially deprecated though.
Of course many of these issues are also part of C++ since it's mostly a superset of C but in general it's stricter and more strongly typed.
> decltype(auto) f1(){int x = 0; return x;}
> decltype(auto) f2(){int x = 0; return (x);}
> Latter, not former, returns reference to int.
But according to OP, it's not C++ that's irrational, it's the programmers who don't want to use C++.
[0] https://twitter.com/sigfpe/status/857748171778252800 [EDIT: corrected broken link]