|
|
Posted by Jerry Stuckle on 07/31/06 15:30
Tony Marston wrote:
> "Jerry Stuckle" <jstucklex@attglobal.net> wrote in message
> news:Fs6dnZzOr4BKU1HZnZ2dnUVZ_vydnZ2d@comcast.com...
>
>>Tony Marston wrote:
>>
>>>"Jerry Stuckle" <jstucklex@attglobal.net> wrote in message
>>>news:-o2dnUSBY-LaCFbZnZ2dnUVZ_sudnZ2d@comcast.com...
>>>
>>>
>>>>Gertjan Klein wrote:
>>>>
>>>>
>>>>>Shelly wrote:
>>>>>
>>>>>[Snip a lot of comments I don't disagree with]
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>If Java were not case sensitive would it still work? Yes. Is it
>>>>>>essential to the language? No. Does it bring benefits? Absolutely.
>>>>>
>>>>>
>>>>>No, it does not. What you have described are conventions used in the
>>>>>case of symbols to make their "type" (constant, variable, function,
>>>>>whatever) clear. These conventions are useful for languages that have no
>>>>>other means to distinguish between these types. I've seen nobody
>>>>>disputing their usefulness. (Note that you can make a THISTHING that is
>>>>>not a constant, and a thisThing that is not a variable. The only meaning
>>>>>of the case used is in the programmer's mind.)
>>>>>
>>>>>The problem with case sensitive languages is that thisThing and
>>>>>THISTHING are entirely different. That means they can both exist at the
>>>>>same time. This can lead to problems in the hands of sloppy or c00l
>>>>>programmers. I see no benefit in having two "things" with the exact same
>>>>>name, differing only in case, meaning two entirely different things.
>>>>>
>>>>>Gertjan.
>>>>
>>>>Gee, a and b can exist at the same time, as can x and y.
>>>>
>>>>thisThing and THISTHING are two different variable names - and can exist
>>>>at the same time.
>>>>
>>>>And yes, it's a problem to sloppy programmers.
>>>>
>>>>And there are definite benefits. For instance, "Customer" can be a
>>>>class, while "customer" an object of that class. And CUSTOMER is a
>>>>defined value. Three different identifiers meaning three different
>>>>things.
>>>>
>>>>But if you're never worked on a multi-programmer project in a case
>>>>sensitive language you may not understand the benefits.
>>>
>>>
>>>I have worked for 25+ years with case INsensiive languages, and I cannot
>>>see any advantages, only problems.
>>>
>>
>>
>>And I have worked almost 40 years in case INsensitive languages, and
>>almost 25 years in case SEnsitive languages. I see a definite advantage,
>>and fewer problems.
>
>
> Can you identify any problem where case sensitivity is the only solution?
> Are you not aware of the problems which case sensitivty can cause?
>
No, because you have never identified any problems caused by case
sensitivity - despite many people asking you about them.
>
>>Of course, if you would have spent 25+ years in Assembler you wouldn't see
>>an advantage to COBOL or FORTRAN, either - much less C or C++.
>>
>>You remind me of a guy I knew when working for IBM back in 1990. He
>>couldn't see any advantage to C++ or OO in general. He'd never used them
>>so they must not be any good. Guess that's why they didn't take off.
>
>
> I never used C or C++ because one of my employers used them. I started using
> OO when I switched to a language that supported it.
>
Gee, I used them even though my employers never did. I spent the effort
to learn them on my own. It made me more marketable, amongst other things.
>
>>And I guess that's why case sensitive languages never took off.
>>
>>ROFLMAO!
>>
>>Another one for my "Tony Marston Chronicles - An Example of Extreme
>>Stoopidity"
>
>
> So I guess I'm not on your Christmas List then?
>
I don't know - maybe I should send you a signed copy.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
[Back to original message]
|