gerry_lowry (alliston ontario canada)
gerry.lowry at abilitybusinesscomputerservices.com
Fri Mar 6 13:24:59 EST 2009
minor point: subject is "CamelCase". Better would have been "camel case".
"camelCase" might be more descriptive, although "Camel Casing" is frequently seen, e.g.:
"History around Pascal Casing and Camel Casing"
http://en.wikipedia.org/wiki/CamelCase ~~ not authoritive, by nature.
-- this article currently uses also:
UpperCamelCase a.k.a. Pascal Casing (more or less)
Pascal Casing has its own interesting quirks, such as capitalizing both letters of
two letter acronyms and only the first letter of longer acronyms.
Both Pascal casing and camel casing belong in some legacy programming languages
to accomodate the language design. Otherwise, to use either except in the description
of source code is probably a bad idea. Not only does this practice defeat search
engine design, it also annoys spell checker software. In c#, I'll probably use both,
e.g.: http://msdn.microsoft.com/en-us/library/ms229002.aspx, especially
http://msdn.microsoft.com/en-us/library/ms229043.aspx "Capitalization Conventions".
The problem is programming requires more attention than English and other languages
where word order and letters can be scrambled and the meaning still obvious to
appropriately literate human readers.
Thatz mi tow sents worth abowt caml kaysing. (sic)
More information about the IAEP