language agnostic - Runtime bugs due to case-sensitivity in (variable) names -


We recenly had a problem () where there was a runtime bug in which the case could be due to the sensitivity (variable) name and It was OS based, it was in the ANLR, but I am generally thinking that there are common cases (in any language) where names differ, compile the program, but there will be runtime errors due to name collision Are there. Can there be a difference between Unix and Windows?

As a possible example, I can create two Java classes in the same package: Foo in Foo.java and foo in foo.java when I can not do this on Windows? If not, then what is trapped by the compiler and what prevents the similarity of the case? And how do other common languages ​​deal with this problem?

[Of course I do not try to do this deliberately, but crawling in errors and I depend heavily on Compiler to find them.]

< / P>

This is not a matter of great concern for most people


Comments

Popular posts from this blog

c# - How to capture HTTP packet with SharpPcap -

jquery - SimpleModal Confirm fails to submit form -

php - Multiple Select with Explode: only returns the word "Array" -