|
|
Posted by Richard Levasseur on 07/31/06 14:37
Tony Marston wrote:
> "Richard Levasseur" <richardlev@gmail.com> wrote in message
> news:1154304261.705624.29410@75g2000cwc.googlegroups.com...
> >
> > Chung Leong wrote:
> >> Andrew DeFaria wrote:
> >> > thisThing and THISTHING *are* two entirely different things! We all
> >> > deal
> >> > with this on a constant bases when "thisThing" and "THISTHING" come
> >> > into
> >> > programs as far as the data stream is concerned. Sure we all know how,
> >> > and often use, case insensitive comparisons precisely because they are
> >> > different. Why then should it be any different when it comes to
> >> > variable
> >> > names inside a program? What you can't tell the difference between the
> >> > two? They don't even look the slightest bit different to you?!? If not
> >> > then that's *your* problem brought about by your narrow minded
> >> > insistence that they are the same when they are not.
> >>
> >> As we all know, thisThing is on first, THISTHING is on second, and
> >> ThisThing is on third. Obviously thisThing can't play first and second
> >> at the same time, so THISTHING has to be on second as we need ThisThing
> >> on third and whatThing only know how to play short.
> >>
> >> I don't know why you said thisThing and THISTHING are entirely
> >> different things. thisThing is on first. THISTHING is on second.
> >> entirely different things is in center and we only got one of him.
> >
> > So its settled.
> > The Three Stooges agree: Case Sensitivity is a Good Thing (tm) ha!
>
> Only in the minds of a few. Case sensitivity was introduced as a programmer
> convention to get around the problem caused by some languages which cannot
> identify the difference between a variable, a constant, a function and a
> method. These small minded individuals are now making this programmer
> convention into a language requirement despite the fact that
> a) They cannot identify a problem where case sensitivity is the solution.
> b) Case sensitivity causes more problems than it solves.
>
Part of why we have case sensitivity is because its much easier (and
faster) to implement in a parser. It has little to do with programmer
preference. However, it has grown into a feature most people want.
Additionally, the case sensitivity of a language has no bearing on how
easy it is to determine if a token is a variable, function call, object
instantiation, etc. This is determined by the grammar rules and syntax
of the language. And, if the grammer requires certain tokens to be of
a certain case, then its not a very good case-insensitive language.
Again, case has absolutely nothing to do with how easy it is to
identify what token a string of characters are.
Finally: My whole previous post was a joke. Lighten up. The shift key
isn't the end of the (programming) world.
> --
> Tony Marston
> http://www.tonymarston.net
> http://www.radicore.org
Navigation:
[Reply to this message]
|