Friday, February 1, 2002 11:29 AM
I've inherited a code base with the following problem:
This translates into compiled code of:
AAAServiceDetail AAAServiceDetail = new AAAServiceDetail();
Obviously, this is extremely bad form. Naming your instantiation of a class the same as the class itself leads to a lot of confusion. What I'm looking for is a strong technical reason why this shouldn't be done this way. The code will compile and run, but now we're experiencing some errors, and this code is suspect.