Google


   


You are here: CodeIdol.com > C++ > C++ Coding Standards: 101 Rules, Guidelines, and Best Practices > Avoid Inheriting From Classes That Were Not Designed To Be Base Classes

SAVE
Digg
Shown on del.icio.us del.icio.us
See Whos Talking About This on Technorati Technorati
I've Reddit reddit

C++ Coding Standards: 101 Rules, Guidelines, and Best Practices



35. SummaryDiscussionExamplesReferences...



Some people don't want to have kids: Classes meant to be used standalone obey a different blueprint than base classes (see Item 32). Using a...

read more: Summary


Using inheritance when it is not needed betrays a misplaced faith in the power of object orientation. In C++, you need to do specific things...

read more: Discussion


Example: Composition instead of public or private inheritance. What if you do need a localized_string that is "almost like string, but with some more state...

read more: Examples


[Dewhurst03] §70, §93 • [Meyers97] §33 • [Stroustrup00] §24.2-3, §25.2...

read more: References

SAVE
Digg
Shown on del.icio.us del.icio.us
See Whos Talking About This on Technorati Technorati
I've Reddit reddit

You are here: CodeIdol.com > C++ > C++ Coding Standards: 101 Rules, Guidelines, and Best Practices > Avoid Inheriting From Classes That Were Not Designed To Be Base Classes


ADBRITE ads links
   
Related tags







Popular Categories
Unix books and guides

AJAX popular information
C# language guides
Windows books and cookbooks

.......








Business Key Top Sites

be number one
rate your site




    С 2009 года мы стали переводить структура сайта на различные языки. Сайт теперь будет содержать книги не только на английском языке, но также и на других европейских языках, в том числе и на Русском языке.

    Русский Polski Francais Deutsch
    support sitemap terms

© CodeIdol Labs, 2007 - 2009