Google


   


You are here: CodeIdol.com > C++ > C++ Coding Standards: 101 Rules, Guidelines, and Best Practices > Give One Entity One Cohesive Responsibility

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



5. SummaryDiscussionExamplesReferences...



Focus on one thing at a time: Prefer to give each entity (variable, class, function, namespace, module, library) one well-defined responsibility. As an entity grows,...

read more: Summary


A good business idea, they say, can be explained in one sentence. Similarly, each program entity should have one clear purpose. An entity with several disparate...

read more: Discussion


Example 1: realloc. In Standard C, realloc is an infamous example of bad design. It has to do too many things: allocate memory if passed...

read more: Examples


[Henney02a] • [Henney02b] • [McConnell93] §• [Stroustrup00] §3.8, §4.9.4, §23.4.• [Sutter00] §10, §12, §19, §23 • [Sutter02] §1 • [Sutter04] §37-40...

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 > Give One Entity One Cohesive Responsibility


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