|
|
Posted by Jerry Stuckle on 11/27/39 11:54
Tony Marston wrote:
> "Richard Levasseur" <richardlev@gmail.com> wrote in message
> news:1154356646.234029.143460@b28g2000cwb.googlegroups.com...
>
>>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.
>
>
> I disagree. Most of the languages I have worked with over the past 25+ years
> have been totally insensitive to case. When your consider how slow the
> processors were all that long ago, the compiler developers chose to
> implement case insensitivity with its slight overhead instead saving a few
> cpu ycles by intoducing case insensitivty.
>
>
>>It has little to do with programmer preference.
>>However, it has grown into a feature most people want.
>
>
> Most people don't *want* this "feature", they are forced into it. When you
> have worked for many years with case insensitive software then encounter the
> problems created with case sensitive software you realise what a stupid idea
> it really is. Given the choice most programmers would chosse software which
> creates fewer problems for them, wich means choosing case insensitive
> software.
>
You don't know what "most people" want or don't want, Tony. You don't
speak for me or many other people in this group, for instance. Neither
do most programmers I know agree with you.
>
>>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.
>
>
> Then why is it that some posters have created their own standards whereby
> the use of case identifies whether something is a constant, variable,
> function or method, and they now want to enforce those standards on eeryone
> else?
>
Yes, why are you trying to create your own standards? Posters aren't
creating standards based on case sensitivity - the world is. It isn't
one or two people - it's the majority of professional programmers using
these standards. And not having case sensitivity takes a valuable tool
away from us.
>
>>Finally: My whole previous post was a joke. Lighten up. The shift key
>>isn't the end of the (programming) world.
>
>
> I still maintain my position that case sensitive software creates more
> problems than it solves, therefore it is a Bad Thing (tm).
>
So? Kwitcherbitchen and to back to your beloved COBOL. We're not
stopping you.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
Navigation:
[Reply to this message]
|