Unity not using Microsoft's C# naming rules

[andyz]

woh I thought this topic was done as it was pointed out in another thread that Unity are mostly going ‘by the book’ now.

@Kiwasi

I guess my key point is that conceptually properties pretend to be fields. So it makes sense to use a naming convention that lets you switch between the two without having to refactor any of the consuming code. The typical unity convention of using camel case for both properties and fields does this.

The Microsoft convention of using different cases doesn’t do this. It means if I ever want to switch between a field and a property, I have to refactor consuming code. Which is bad. Especially if there is more then one dev working on a project.

Its not so much that I always want to use fields or properties. Its that I want to have a choice to be able to switch between them at will throughout the project. And the Microsoft standard only makes sense if you restrict yourself to always using properties.

It seems curious that properties and variables appear the same in calling but one is capitalised - which might answer the question for why it is that way. You might not be able to set or get a property and there might be more cost involved in get/set of it thus the capital naming reminds you it is a property not a simple field. Refactoring is now simple