I can remember Convert class in .net which is named not in accordance with the guide lines. Any more examples?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In Java,
java.lang.System.arraycopy– note the lowercase second c.Also
NullPointerExceptionin Java is better asNullReferenceExceptionin .NET.AppDomainviolates the convention of normally not using abbreviations.Control.IDviolates the explicit convention of Pascal-casing ID to ‘Id’ and Camel-casing it to ‘id’.EDIT: Due to popular demand, a couple more… although they’re more just badly named than convention-defying.
SortedListin .NET – that explains what the implementation is, but doesn’t give the correct impression about what the API is – that of a dictionary.Type.MakeGenericType– it makes a constructed type. DittoMethodInfo.MakeGenericMethod.