Linked by Thom Holwerda on Wed 2nd Dec 2009 23:17 UTC
Features, Office A few weeks ago, we talked about how the rise of computing, a field wherein English is the primary language, is affecting smaller languages, and more specifically, the Dutch language (because that's my native tongue). Of course, it's not just the smaller languages that are affected - English, too, experiences the pressure.
E-mail Print r 6   · Read More · 59 Comment(s)
Thread beginning with comment 397609
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: camel case in programming
by ebasconp on Thu 3rd Dec 2009 01:39 UTC in reply to "camel case in programming "
ebasconp
Member since:
2006-05-09

Agreed,

The rational on this is because compilers use identifier names [variables, classes, functions, methods, etc.] as an entity that just contains alphanumerical characters and a reduced number of symbols.

Space is generally treated as a separator, so, if a variable is called "my salary" instead of "mySalary" would create ambiguity for the compiler: "what is the variable name? 'my'? if the variable name is 'my'... what the hell is 'salary' here? I do not know a reserved word called 'salary' and after the variable 'my' I expect an operator or a function name to invoke"... or something like that ;)

Reply Parent Score: 2

Doc Pain Member since:
2006-10-08

Space is generally treated as a separator, so, if a variable is called "my salary" instead of "mySalary" would create ambiguity for the compiler: "what is the variable name? 'my'? if the variable name is 'my'... what the hell is 'salary' here? I do not know a reserved word called 'salary' and after the variable 'my' I expect an operator or a function name to invoke"... or something like that ;)


Quite easy: "my" is the (data)type of "salary". :-)

Reply Parent Score: 2