4 ms·
What is wrong with different naming conventions for fields vs. properties, and methods? It makes it immediately obvious what is what at a glance. *Honest ques
by de90 15y ago
What is wrong with different naming conventions for fields vs. properties, and methods? It makes it immediately obvious what is what at a glance.
*Honest question - I first learned programming with C#, and so those conventions seem 'correct' to me.
- masklinn 15y ago> What is wrong with different naming conventions for fields vs. properties, and methods? It makes it immediately obvious what is what at a glance. Which is precisely one of the problems of properties in C#, it makes fields and properties look and feel extremely different from the outside which violates the uniform access principle. As I noted, ideally C# should not have public fields in the first place.