|
|
Posted by Tony Marston on 10/14/40 11:35
"Jerry Stuckle" <jstucklex@attglobal.net> wrote in message
news:4Lmdnd9W-pNukTPenZ2dnUVZ_tGdnZ2d@comcast.com...
> Tony Marston wrote:
>>>Neither I nor anyone else needs to "give a convincing reason...". The
>>>bottom line is - that's the way things are, and it is supported by a vast
>>>majority of programmers.
>>>
>>>However, there have been other reasons mentioned in this topic. But I
>>>suspect none of them are "good enough" for you.
>>>
>>>And I haven't heard any good reasons why NOT to welcome it. Just saying
>>>$Foo and $fOO shouldn't point to different variables doesn't make it. To
>>>me they ARE different variables (although I wouldn't do this myself).
>>
>>
>> Why wouldn't you do it yourself? Because it would lead to confusing and
>> unmentionable code, that's why. Any language that allows a programmer to
>> create confusing and unmaintainable code is a BAD language in my book.
>
> You can create confusing and unmaintainable code in ANY language - even
> COBOL. Case sensitivity has NOTHING to do with it.
Case-sensitivity is the whole point of this thread. Any language that has a
feature which can be abused and which produces unmaintainable code is a BAD
language. Any language that allows the same variable or function name to
exist in different combinations of upper and lower case, and to give a
different meaning to each of those combinations, is a BAD language. Case is
irrelevant in all human languages, so it should be irrelevant in all
computer languages.
Why do most modern languages exclude the GOTO statement? Because it is
considered BAD.
Jus because some computer languages have case-sensitivity does not make it a
good idea It is just a bad idea that is being perpetuated against all logic
and reason.
Navigation:
[Reply to this message]
|