Designing and Coding Reusable C++

by Margaret A. Ellis and Martin D. Carroll

Book Overview

One of the most important benefits of programming in C++ is its reuse capabilities. This work illustrates all of the tradeoffs involved in writing reusable code, and is intended for novice and experienced programmers alike. Features include: discussion of the topics related to the software development of code reusability in the design of interfaces, the efficiency of implementations, portability and compatibility; definition of the concept of functions...

• Format: Paperback
• Language: English
• ISBN: 020151284X
• ISBN13: 9780201512847
• Release Date: May 1995
• Publisher: Addison-Wesley Professional
• Length: 336 Pages
• Weight: 1.10 lbs.
• Dimensions: 1.1" x 6.2" x 9.2"

Customer Reviews

Solid Advice for Library Designers

In view of the fact that a previous reviewer recommended reading Scott Meyers instead of this book, I thought you might like to see what Scott Meyers has to say about Designing and Coding Reusable C++. Simply put, the book is on my short list of recommended reading for C++ programmers. I describe things this way in my More Effective C++: "If you have anything to do with the design and implementation of C++ libraries, you would be foolhardy to overlook Designing and Coding Reusable C++. Carroll and Ellis discuss many practical aspects of library design and implementation that are simply ignored by everybody else. Good libraries are small, fast, extensible, easily upgraded, graceful during template instantiation, powerful, and robust. It is not possible to optimize for each of these attributes, so one must make trade-offs that improve some aspects of a library at the expense of others. Designing and Coding Reusable C++ examines these trade-offs and offers down-to-earth advice on how to go about making them."

Read this if reuse is important to you.

I found the entire book worthwhile and hope for a new edition now that C++ is an international standard. Code reuse is easier with good documentation. One chapter contains important advice for documenting the design and interface to classes. An example (or even a reference to) a good class "design paper", tutorial, and class reference would be a great addition.