Naming Convention Violation On The .NET BCL
Published June 19, 2007I wonder who is responsible for this:
public class Formatter
{
// ...
protected ObjectIDGenerator m_idGenerator;
protected Formatter m_objectQueue;
// ...
}
Can you spot how many naming conventions were violated here?
IMO conventions are always related to people willing to comply with them. Then to avoid long debates about naming conventions, you could write “Microsoft naming conventions” 😉
That’s one of the problems with public fields, they’re now burned into the interface and can never be removed, only obsoleted.
That’s why this is more a class library design guideline violation that a naming convention violation:
Do not use instance fields that are public or protected (…)
http://msdn2.microsoft.com/en-us/library/ta31s3bc(VS.71).aspx