News for hackers. Stuff that matters.
Re:Rob Pike: Notes on Programming in C by amh on Tuesday November 09, 2010 @04:06PM (#1887903)
I think "godisnowhere" is more an example of a straight-up badly chosen name (identifiers should not be complete sentences) rather than a case where caps are better than lowercase.

I'm not against camelcase and its variants, but there are a wide variety of naming standards using caps, it's quite possible to get mixed up between them and introduce ambiguity or worse (referring to the wrong variable).

Re:Rob Pike: Notes on Programming in C by TheNewAndy on Wednesday November 10, 2010 @04:41AM (#1889764)
I believe the intention of this name was the parsing ambiguity of the word "nowhere" when you don't have word delimiters, not as an example of an actual name, or a statement about the location of God :)
Re:Rob Pike: Notes on Programming in C by epo on Wednesday November 10, 2010 @07:01AM (#1890000)
Surely, that's his point, putting an ambiguity into a variable name is just asking for trouble, choose a better name.
Re:Rob Pike: Notes on Programming in C by TheNewAndy on Wednesday November 10, 2010 @07:27AM (#1890041)
The ambiguity isn't in the name on its own "God is nowhere". It is in the combination of that name, and a bad naming convention.

If you had a naming convention which prohibits vowels, then the identifier "shrt" is ambiguous because it could be "short" or "shirt". That doesn't mean that "short" is a bad name for an identifier.