minor point: subject is "CamelCase". Better would have been "camel case".
"camelCase" might be more descriptive, although "Camel Casing" is frequently seen, e.g.: http://blogs.msdn.com/brada/archive/2004/02/03/67024.aspx "History around Pascal Casing and Camel Casing" http://en.wikipedia.org/wiki/CamelCase ~~ not authoritive, by nature. "CamelCase" -- this article currently uses also: lowerCamelCase LCC 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) regards gerry (lowry) _______________________________________________ IAEP -- It's An Education Project (not a laptop project!) [email protected] http://lists.sugarlabs.org/listinfo/iaep
