StudlyCaps [LWN.net]

StudlyCaps

Posted Oct 14, 2010 22:00 UTC (Thu) by pr1268 (guest, #24648)
In reply to: Russell: On C Library Implementation by ncm
Parent article: Russell: On C Library Implementation

I always thought it was CamelCase (with the BactrianCamelCase and dromedaryCamelcase variants). ;-)

to post comments

StudlyCaps

Posted Oct 15, 2010 8:20 UTC (Fri) by rvfh (guest, #31018) [Link] (4 responses)

I think thisIsCamelCase.

StudlyCaps

Posted Oct 15, 2010 10:21 UTC (Fri) by peregrin (guest, #56601) [Link] (3 responses)

Depends on whether the camel is currently standing upright or drinking (StandingCamelCase vs. drinkingCamelCase).

StudlyCaps

Posted Oct 15, 2010 17:02 UTC (Fri) by marcH (subscriber, #57642) [Link]

> StandingCamelCase vs. drinkingCamelCase

Brilliant! Noted.

StudlyCaps

Posted Oct 21, 2010 22:28 UTC (Thu) by speedster1 (guest, #8143) [Link]

> (StandingCamelCase vs. drinkingCamelCase)

Depending on what it's drinking, it could be dRInk1ngcAM3LCaSE

StudlyCaps

Posted Oct 22, 2010 21:54 UTC (Fri) by foom (subscriber, #14868) [Link]

Or, if you're using the Go language, you have privateCamelCase and PublicCamelCase. :)

In Go the rule about visibility of information is simple: if a name (of a top-level type, function, method, constant or variable, or of a structure field or method) is capitalized, users of the package may see it. Otherwise, the name and hence the thing being named is visible only inside the package in which it is declared. This is more than a convention; the rule is enforced by the compiler. In Go, the term for publicly visible names is ''exported''.

Woo.