> you should always prefer private to protected and protected to public It's well known that protected is not any safer than public. Anybody can inherit and us

> you should always prefer private to protected and protected to public It's well known that protected is not any safer than public. Anybody can inherit and use it. You can still make members private in structs. It's only less redundant: class X { public: stuff; private: other stuff; }; vs struct X { stuff; private: other stuff; }; > Another reason to use "class" is because it's OOP terminology. There's no notion of "struct" in OOP That's cargo cult programming. Using "class" doesn't make your code OO. The language we are programming in is C++, not OOP.