Date:         Mon, 30 Nov 2009 12:59:00 -0500
Reply-To:     Peter Flom <peterflomconsulting@mindspring.com>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Peter Flom <peterflomconsulting@MINDSPRING.COM>
Subject:      Re: OT: Thursday Theory
Comments: To: "Fehd,Ronald J. (CDC/CCHIS/NCPHI)" <rjf2@CDC.GOV>
Content-Type: text/plain; charset=UTF-8

>Subject: OT: Thursday Theory

Errr ... RonFehd ... today is notThursday :-)


>
>CamelCase
>
>YeahBut this rant is more about initial lowcase with internalCaps.
>as stated:
>
>"Thus styled, the word has a hump in the middle.
>I could print it here to show you,
>but I refuse to allow my prose to be so disfigured."
>
>http://www.nytimes.com/2009/11/29/magazine/29FOB-onlanguage-t.html
>
>"The Greeks started it,
>Irish and English priets contributed to its popularity,
>...."
>
>My very own personal reasons for using CamelCase:
>
>* length of variable name = 32
>
>* hate underlines, wish we could use hyphens,
>  but either makes the names longer than 32
>
>* HATE ALL CAPS
>
>* lowercase inappropriate for Proper Nouns,
>  i.e.: DataSetNames, VariableNames, etc.
>
>* have a style sheet which encourages
>
>* SAS is a case-insensitive language
>  which doesn't mean I have to be either:
>  * insensitive
>  * in sensitive
>

Yet more reasons for CamelCase ...

I use R and I use SAS.

R is case sensitive, SAS is not.
In R you can use . in a veriable name, but should not use _; in SAS, just the opposite.
But both can use CamelCase.

Now, if only my clients would give me Excel sheets that SAS could translate into CamelCase instead of the awful mess of things like _Black__in_G_nrl_pop and such illegible drivel....

Peter
confused by Case

Peter L. Flom, PhD
Statistical Consultant
Website: www DOT peterflomconsulting DOT com
Writing; http://www.associatedcontent.com/user/582880/peter_flom.html
Twitter:   @peterflom