Hm,
this is something I never understand.
If I do things case sensitive then there is a sense in using a var named Loop and an other namend loop in the same scope. So how could any IDE catch in if I code like this? If I avoid names like the example then otoh there is no need for it anyway.

This all is a kind of rubbish some curlish compiler coder has done in the days of yore where a simple UPPER (or the like) was to much memory and to much runtime. And the believers of low level languages think it is a commandment.

Agnes

>WIth the right IDE, that rarely happens as the IDE catches the mistake and tells you.
>
>>The point is that it has nothing in the "pro" list and lots in the "con" list. There is really no good reason for case-sensitivity. You're constantly doing something or using some tool in order to get it right. And not every case sensitive language has those tools. Take JavaScript for example. It trips you up. You're writing some complex code and get fooled by an error that actually turns out to be a case issue when you're looking past that to something more complex. Then you realize its a stupid case issue. We have enough troubles in this industry with the relentless change, integration of complex technologies, etc., etc. etc. We don't need to trip ourselves up with stupid issues like case-sensitivity.