If that were the case then int * x would be a compiler error. Seems like Ritchie just made a mistake and forgot to point out that int* is a type, so everyone just kept making the same mistake.
No, it wouldn't because whitespace largely insignificant. In your example, the "thing on the right" is still* x. The space doesn't matter.
What's actually more annoying about C is that when you declare something like int f(int a[4]) that it's highly deceptive since C doesn't have array parameters.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
If that were the case then
int * xwould be a compiler error. Seems like Ritchie just made a mistake and forgot to point out thatint*is a type, so everyone just kept making the same mistake.No, it wouldn't because whitespace largely insignificant. In your example, the "thing on the right" is still
* x. The space doesn't matter.What's actually more annoying about C is that when you declare something like
int f(int a[4])that it's highly deceptive since C doesn't have array parameters.