int score, playerScore.void DoSomething().class Player, PlayerStats.Objects is the one I'm on the fence about, it's a variable of sorts so this could be done as: Player john = new Player. The problem here is that when it comes to names like that, grammar dictates that I should capitalise a name, and I often do out of habit.
So Player John = new Player reads 'better' to me but breaks the variable convention.
I feel it may be an exception because when I look at say a message box code: MessageBox.Show(""), this has each word upper case which would be broken if I was calling a method for john such as: john.ShowStats();
What I also find odd in my book is that class fields are capitalised but they are just a variable
class Elephant {public int EarSize;public string Name;public void WhoAmI() {MessageBox.Show("My ears are " + EarSize + " inches tall.",Name + " says...");}} I need to choose something and stick to it, I'm just wondering what others use. I suppose for what I'm doing it doesn't matter too much as only I'll ever be working on my projects but it's good practice to use something that most others do.
.
I wouldn't say there is a "global standard" but most languages and shops use camal casing with the exception being .Net which uses what you are describing (upper casing the first letter of each word...not even sure what this is called).
In the end, it really doesn't matter as long as you are consistent with your naming. Basically though, things starting with upper case letters are classes (models, services etc), so it is easy to identify if you are dealing with a class or a static class.