Posted by Jerry Stuckle on 10/17/57 11:35
Tony Marston wrote:
> "Jerry Stuckle" <jstucklex@attglobal.net> wrote in message
> news:_ZKdnVmWBtTBOTDenZ2dnUVZ_sCdnZ2d@comcast.com...
>
>>Colin Fine wrote:
>>
>>>Nobody's given a convincing reason why case sensitivity is better. (The
>>>nearest to it is the stuff about the cost of doing the comparisons. That
>>>might have been an issue when Unix and C started up, but it's not very
>>>convincing today.).
>>>
>>>
>>>You may well be right that it will become increasingly difficult to find
>>>systems that aren't case insensitive. But I've yet to hear a reason why
>>>this is to be welcomed, while I do know a couple of reasons not to
>>>welcome it.
>>>
>>>Colin
>>>
>>
>>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.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
[Back to original message]
|