C++ FAQ LITE — Frequently Asked Questions
(Copyright © 1991-98, Marshall Cline, cline@parashift.com)

Improve network response:

• Use the closest mirror site: USA, Canada, Finland, France, Germany, Spain, Taiwan, U.K..
• Browse the FAQ off-line: Use the one-click download feature to get your own local copy.

Look up stuff:

• Look up a generic topic with the table of contents (35 coarse-grained topics).
• Look up a specific topic with the extensive subject index (723 fine-grained topics).
• Look up the changed topics with the chain of recent changes (20 changes for 5/98 and 6/98).

Table of Contents:

• [1] Copying permissions
• [2] On-line sites that distribute this document
• [3] C++-FAQ-Book versus C++-FAQ-Lite
• [4] Recent changes to this document
• [5] Netiquette when posting to comp.lang.c++
• [6] Big Picture issues
• [7] Classes and objects
• [8] References
• [9] Inline functions
• [10] Constructors
• [11] Destructors
• [12] Assignment operators
• [13] Operator overloading
• [14] Friends
• [15] Input/output via <iostream.h> and <stdio.h>
• [16] Freestore management
• [17] Exceptions and error handling
• [18] Const correctness
• [19] Inheritance — basics
• [20] Inheritance — virtual functions
• [21] Inheritance — proper inheritance and substitutability
• [22] Inheritance — abstract base classes (ABCs)
• [23] Inheritance — what your mother never told you
• [24] Inheritance — private and protected inheritance
• [25] Coding standards
• [26] Learning OO/C++
• [27] Learning C++ if you already know Smalltalk
• [28] Reference and value semantics
• [29] How to mix C and C++
• [30] Pointers to member functions
• [31] Container classes and templates
• [32] Class libraries
• [33] Compiler dependencies
• [34] Miscellaneous technical issues
• [35] Miscellaneous environmental issues

 E-mail the author
[ C++ FAQ Lite | Table of contents | Subject index | About the author | © | Download your own copy ]
Revised Jun 29, 1998

Contents of this web page do not and are not intended to reflect the views of CERFnet. The author of this home page is solely responsible for its contents.