Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Which naming convention do you use for local constants in C# and why?
const int Pi = 3;
const int pi = 3;
It seems the trade-off is between lower camel-case indicating restricted scope, and upper camel-case being more readable and easier to move to a class level. I’ve noticed StyleCop prefers upper camel-case.
I’m used to upper case (pascal case) for everything except variables and fields. Global constants are an exception to the fields, I don’t know why, probably because they are public in some cases. Local constants are also lowercase so.
It’s just a matter of taste imo. Of course, within a product / team, there should be an agreement.
On the other hand, our coding guideline requires full uppercase for constants, this would be
PIin this case. I don’t like this because upper cases are hard to read and need underlines for separation (which is against code analysis rules). Nobody follows this guideline anymore.