Programming Language

2009-05-15

camelCase

Image by coderkind via Flickr

camelCase

A variable in a programming language is sait to be camelCased when all words but the first are capitalized. This practice contrasts with the C tradition of either running syllables together or marking syllable breaks with underscores; thus, where a C programmer would write thisverylongname or this_very_long_name, the camelCased version would be thisVeryLongName. This practice is common in certain language communities (formerly Pascal; today Java and Visual Basic) and tends to be associated with object-oriented programming.

Compare {BiCapitalization}; but where that practice is primarily associated with marketing, camelCasing is not aimed at impressing anybody, and hackers consider it respectable.

Related articles by Zemanta

camelCase (what-is-the-meaning-of.blogspot.com)
Programming Scala (oreilly.com)
Ruby as the Joker (byzantinereality.com)
On programming language design (math.andrej.com)
PascalCasing (what-is-the-meaning-of.blogspot.com)
Underscoring A Point (codebetter.com)
MapReduce, Map Reduce, Map/Reduce or Map-Reduce? (lexemetech.com)
NHibernate and 'Invalid Index N for this SqlParameterCollection with Count=N error' (devlicio.us)
JavaScript for PHP Developers (slideshare.net)
CodeSOD: Fred Code (thedailywtf.com)
Scala seems to be fun (ribomation.com)
RoBeDo Offers Three (ubergizmo.com)
Volunteer Programming For Dummies? (ask.slashdot.org)
Visual Studio 2008 Express Editions (lockergnome.com)
O'Reilly: Upcoming Javascript training class with Douglas Crockford in San Francisco (woork.blogspot.com)

Marcadores: CamelCase, Common, Computer programming, Java, Languages, Object-Oriented, Object-oriented programming, Programming, Programming language, Visual Basic

# 5/15/2009 12:31:00 AM, Comentários, Links para esta postagem,

2009-02-18

user

Someone doing `real work' with the computer, using it as a means rather than an end. Someone who pays to use a computer. See {real user}.
A programmer who will believe anything you tell him. One who asks silly questions. [GLS observes: This is slightly unfair. It is true that users ask questions (of necessity). Sometimes they are thoughtful or deep. Very often they are annoying or downright stupid, apparently because the user failed to think for two seconds or look in the documentation before bothering the maintainer.] See {luser}.
Someone who uses a program from the outside, however skillfully, without getting into the internals of the program. One who reports bugs instead of just going ahead and fixing them.
The general theory behind this term is that there are two classes of people who work with a program: there are implementors (hackers) and {luser}s. The users are looked down on by hackers to some extent because they don't understand the full ramifications of the system in all its glory. (The few users who do are known as real winners.) The term is a relative one: a skilled hacker may be a user with respect to some program he himself does not hack. A LISP hacker might be one who maintains LISP or one who uses LISP (but with the skill of a hacker). A LISP user is one who uses LISP, whether skillfully or not. Thus there is some overlap between the two terms; the subtle distinctions must be resolved by context.