Large-scale C++ Software Design
Addison-Wesley, 1996 - 846 Seiten
This is the definitive book for all C++ software professionals involved in large development efforts such as databases, operating systems, compilers, and frameworks. It is the first C++ book that actually demonstrates how to design large systems, and one of the few books on object-oriented design specifically geared to practical aspects of the C++ programming language. In this book, Lakos explains the process of decomposing large systems into physical (not inheritance) hierarchies of smaller, more manageable components. Such systems with their acyclic physical dependencies are fundamentally easier and more economical to maintain, test, and reuse than tightly interdependent systems. In addition to explaining the motivation for following good physical as well as logical design practices, Lakos provides you with a catalog of specific techniques designed to eliminate cyclic, compile-time, and link-time (physical) dependencies. He then extends these concepts from large to very large systems. The book concludes with a comprehensive top-down approach to the logical design of individual components. Appendices include a valuable design pattern Protocol Hierarchy designed to avoid fat inte
Was andere dazu sagen - Rezension schreiben
Es wurden keine Rezensionen gefunden.
PHYSICAL DESIGN CONCEPTS
14 weitere Abschnitte werden nicht angezeigt.
abstraction allocated allow argument array avoid base behavior Chapter char clients compile compile-time complex component Consider const constructs contains conversion cost coupling create defined definition dependencies derived direct directly double dynamic Edge effective encapsulation entire error example external factor Fendif forced fully given global graph header file ifndef illustrated implementation implied independent individual initialization inline instance insulation integer interface internal iterator logical maintain member function memory modified Node object operator package passed performance physical pointer possible prefix presented Principle problem protected reason reduce reference release requires result reuse rules runtime scope Shape short shown in Figure single specific Stack static String subsystem techniques tion unit virtual void wrapper