C++ strategies and tactics / Robert B. Murray.
Material type:
TextSeries: Addison-Wesley professional computing seriesPublication details: Reading, Mass. : Addison-Wesley Pub. Co., c1993.Description: xiv, 282 p. : ill. ; 24 cmISBN: - 0201563827 (pbk. : recycled paper)
- 9780201563825
- QA76.73.C15 .M87
| Cover image | Item type | Current library | Home library | Collection | Shelving location | Call number | Materials specified | Vol info | URL | Copy number | Status | Notes | Date due | Barcode | Item holds | Item hold queue priority | Course reserves | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Books
|
Methodist University Library Main General Stacks | Reference | QA76.73.C15 .M87 (Browse shelf(Opens below)) | Available | 16544 |
Browsing Methodist University Library Main shelves,Shelving location: General Stacks,Collection: Reference Close shelf browser (Hides shelf browser)
|
|
|
|
|
|
|
||
| QA76.73.B3 D455 Simply Visual Basic .NET / | QA76.73.C15 .G68 Programming with C | QA76.73.C15 .G68 Programming with C | QA76.73.C15 .M87 C++ strategies and tactics / | QA76.73.C15 .S79 The C++ programming language / | QA76.73.C153 .A83 A computer science tapestry : | QA76.73.C153 .C66 C++ program design : |
Includes index.
A note about the code examples --
A road map --
The language rules --
Abstraction --
A telephone number abstraction --
Relationships between abstractions --
Worrying about the boundary conditions --
Designing with CRC cards --
In short --
Classes --
Constructors --
Assignment --
Public data --
Implicit type conversions --
Overloaded operators: members or nonmembers? --
Overloading, defaults, and ellipsis --
Const --
Returning references --
Static constructors --
In short --
Handles --
A String class --
Avoiding copies with use counts --
Avoiding recompilations: the Cheshire Cat --
Using handles to hide the design --
Multiple implementations --
Handles as objects --
In short --
Inheritance --
The is-a relationship --
Public inheritance --
Private inheritance --
Protected inheritance --
Conformance to base class abstractions --
Pure virtual functions --
Inheritance details and traps --
In short --
Multiple Inheritance --
Multiple inheritance as set intersection --
Virtual base classes --
Some multiple inheritance details --
In short --
Designing for Inheritance --
The protected interface --
Should you design for inheritance --
Design for inheritance: some examples --
In short --
Templates --
A Pair class template --
Some template details --
Template instantiation --
Smart pointers --
Expression arguments to templates --
Function templates --
In short --
Advanced Templates --
Container classes using templates --
Example: a Block class --
Detailed Block design issues --
Containers with iterators: a List class --
Iterator design issues --
Performance issues --
Constraints on template arguments --
Template specializations --
In short --
Reusability --
Discovery and acquisition --
Robustness --
Memory management --
Alternative memory allocation schemes --
Passing arguments to operator new --
Managing external resources --
Finding memory bugs --
Name collisions --
Performance --
Don't guess, measure! --
Algorithms --
Bottlenecks in dynamic memory allocation --
Inlines --
Tiemann's law --
In short --
Exceptions --
A disclaimer --
Why exceptions? --
An example exception --
Exceptions should be exceptional --
Understanding exceptions --
Blame assessment --
Designing the exception object --
In short --
Moving your project to C++ --
Choosing C++ --
Adopting C++ --
Design and implementation --
Developing an asset base --
A closing thought --
In short.
There are no comments on this title.