Case sensitivity

To avoid confusion and guarantee cross-language interoperation, follow these rules regarding the use of case sensitivity:

Ø Do not use names that require case sensitivity. Components must be fully usable from both case-sensitive and case-insensitive languages. Case-insensitive languages cannot distinguish between two names within the same context that differ only by case. Therefore, you must avoid this situation in the components or classes that you create.

Ø Do not create two namespaces with names that differ only by case. For example, a case insensitive language cannot distinguish between the following two namespace declarations:

namespace ee.cummings;

namespace Ee.Cummings;

Ø Do not create a function with parameter names that differ only by case. The following example is incorrect:

void MyFunction(string a, string A)

Ø Do not create a namespace with type names that differ only by case. In the following example, Point p and POINT p are inappropriate type names because they differ only by case:

System.Windows.Forms.Point p

System.Windows.Forms.POINT p

Ø Do not create a type with property names that differ only by case. In the following example, int Color and int COLOR are inappropriate property names because they differ only by case:

int Color

int COLOR

Ø Do not create a type with method names that differ only by case. In the following example, calculate and Calculate are inappropriate method names because they differ only by case:

void calculate()

void Calculate()