PascalCase. For Everything!
C# is the best example!:
Classes? PascalCase.
Class members (methods and properties)? PascalCase.
Nested Classes? PascalCase.
Constants? Sometimes UPPERCASE, but usually they follow the same usual convention of PascalCase.
Enum members? PascalCase.
Function parameters and local variables? Lower case, thankfully.
It drives me mad! There's no way to tell if RandomIdentifier is a class, property, method, or constant (property) without seeing it being used, or going into the source code, and finding RandomIdentifier.
This sounds really mean, since they're just giving me advice.
But I still detest certain stylistic features. - And if people can't code in a style that's suitable for them, even if it looks alright, and isn't hurting anyone, then I get real steamed.
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.
PascalCase. For Everything!
C# is the best example!:
It drives me mad! There's no way to tell if
RandomIdentifieris a class, property, method, or constant (property) without seeing it being used, or going into the source code, and findingRandomIdentifier.Oh yeah, people that don't use the correct case for certain datatypes is annoying.
Like Constant variables should just be an easy uppercase, but people still are so lazy to do it.
It's not about laze, it's about people using outdated, or plain out wrong casing conventions.
And you'd think this is applicable to all languages with C-grammar. Nope. Apparently in C++ "uPpErCAsE is FoR mAcROs eVen ThOuGh ThEy'rE oUTdAtEd IN mOdErN cOde." - circa a person on r/CPP_Questions.
This sounds really mean, since they're just giving me advice.
But I still detest certain stylistic features. - And if people can't code in a style that's suitable for them, even if it looks alright, and isn't hurting anyone, then I get real steamed.