Lines Matching full:inheritance
1259 <h3 id="Inheritance">Inheritance</h3>
1262 <p>Composition is often more appropriate than inheritance.
1263 When using inheritance, make it <code>public</code>.</p>
1272 defines. In practice, inheritance is used in two major
1273 ways in C++: implementation inheritance, in which actual
1275 <a href="#Interfaces">interface inheritance</a>, in which
1280 <p>Implementation inheritance reduces code size by re-using
1282 Because inheritance is a compile-time declaration, you
1284 errors. Interface inheritance can be used to
1292 <p>For implementation inheritance, because the code
1304 <p>All inheritance should be <code>public</code>. If you
1305 want to do private inheritance, you should be including
1308 <p>Do not overuse implementation inheritance. Composition
1310 inheritance to the "is-a" case: <code>Bar</code>
1344 <h3 id="Multiple_Inheritance">Multiple Inheritance</h3>
1347 <p>Only very rarely is multiple implementation inheritance
1348 actually useful. We allow multiple inheritance only when at
1358 <p>Multiple inheritance allows a sub-class to have more than
1365 <p>Multiple implementation inheritance may let you re-use
1366 even more code than single inheritance (see <a href="#Inheritance">Inheritance</a>).</p>
1371 inheritance actually useful. When multiple implementation
1372 inheritance seems like the solution, you can usually find
1377 <p> Multiple inheritance is allowed only when all
1434 important in the case of <a href="#Multiple_Inheritance">multiple inheritance</a>.
1797 are confused by the semantics of inheritance if a derived
5906 // Spaces around the colon in inheritance and initializer lists.
6108 the use of multiple implementation inheritance</a>;
6111 inheritance to implement COM or ATL/WTL classes and
