>>Do you mean CamelCase? I programmed in Pacal in college, but I'm not sure when this became known as Pascal casing. I consider it a bad technique when the simple case of a variable (or whatever) indicates something. Our brains don't differentiate that. I could refer to you as viv and you might prefer Viv, but you'd know it was you to whom I was referring. You could, in a case sensitie language, make S and s variable names and they'd be different, but it'd be bad technique. Perhaps I'm still not understanding what you're getting at, but imparting meaning via the case of a variable name is a stupid idea regardless of who came up with it.
>
>Oh, I know original post is abou something at codeplex that I didn't read but this one:
>
>"I consider it a bad technique when the simple case of a variable (or whatever) indicates something. Our brains don't differentiate that."
>
>is something that I could strongly disagree. Our brains surely differentiate it. You don't know Turkish, do you?
>
>enbuyukortakbolen
>
>How many words are there?
>
>With no casing is it:
>
>en buyu kort ak bolen
>
>or:
>
>en buyuk ortak bolen
>
>EnBuyukOrtakBolen
>
>now? Brain doesn't differentiate do you think? You are undertaking brain's functionality especially the importance of occipital lobus.
>Cetin

No, I think you were reading into that something I didn't mean. Most programmers to something to differentiate between words. CamelCase or an underscore or thisIsMyVariableName (C programmers love that leading letter to be lowercase). I am assuming that some technique will be employed fairly consistently. What I mean was Total should not be seen as a different variable from total. thisIsMyVariableName should be the same as ThisIsMyVariableName. If you want to use all lowercase and run the words together wih no underscore or whatever, then you will get var names that are hard to read, especially with longer ones. On that we agree.