Reminds me of this from Bartosz' site:

"If you're a fan of object-oriented programming, you might find this 
quotation from the MFC's official Guidelines for Writing Class Library 
Extensions pretty amusing.

    Limit the Use of "Private" in Your Classes. It is important that your 
users be able to use your MFC-friendly classes in ways that you might not 
have originally intended. By keeping the majority of member functions, data 
members, and operators public, you allow for flexibility in their use. In 
MFC, even functions declared in the //Implementation section of a class are 
usually public or protected. " 

http://www.relisoft.com/resource/libs.html

Reply via email to