From: Gavin Kistner <gavin@...>
Date: 2004-02-25T00:35:46+09:00
Subject: Re: Appropriate use of camelCase

On Feb 23, 2004, at 7:11 PM, Kirk Haines wrote:
> This is another perfect example of something that is a religious 
> issue. One can make good arguments for using spaces for indentation, 
> and one can make good arguments for using tabs for indentation.  When 
> one is down in the trenches churning out a solution for a client, what 
> matters most is that one be consistent with whatever one chooses, as 
> there are always going to be people who both agree and disagree with 
> the choice.  Better to just make the choice and then get on with 
> getting the work done.

I agree that what matters is consistency, and what_works_for_you. (See, 
I'm getting the hang of it already! :)

I didn't mean (too much) to start a religious debate. The thing is, I'm 
a blank slate when it comes to Ruby. Sure, I have a bit of baggage from 
past languages, but I'm starting fresh and I want to be clean.

Further, consistency is important not just within my own code, but 
within the community if I plan on ever contributing back. So I want to 
learn to be consistent with whatever prevalent pseudo-standard may 
exist.

Although the topic *is* ripe for a holy war, and some (including 
myself) certainly prefer camelCase in some instances, it appears that 
the vast majority use snake_case for everything but 
ClassAndModuleNames. (Which really, I never thought was in any doubt; I 
can't imagine a class name with an underscore.)

So...as proud as I was of my nouns/verbs rationale for including 
camelCase in method names, I will henceforth use snake_case only for 
method names, UpperCamelCase for class/module names, and 
SHOUTING_AT_THE_TOP_OF_MY_LUNGS case for constants.


Despite the touchy subject, thank you all for your feedback.

(And don't even get me started on the tabs issue! :p)
--
(-, /\ \/ / /\/