How is this section organized?, C++ FAQ

C++ FAQ / Section 25 / FAQ 25.1

Section 25:

25.1	How is this section organized?
25.2	I've been told that I should never use multiple inheritance. Is that right?
25.3	So there are times when multiple inheritance isn't bad?!??
25.4	What are some disciplines for using multiple inheritance?
25.5	Can you provide an example that demonstrates the above guidelines?
25.6	Is there a simple way to visualize all these tradeoffs?
25.7	Can you give another example to illustrate the above disciplines?
25.8	What is the "dreaded diamond"?
25.9	Where in a hierarchy should I use virtual inheritance?
25.10	What does it mean to "delegate to a sister class" via virtual inheritance?
25.11	What special considerations do I need to know about when I use virtual inheritance?
25.12	What special considerations do I need to know about when I inherit from a class that uses virtual inheritance?
25.13	What special considerations do I need to know about when I use a class that uses virtual inheritance?
25.14	One more time: what is the exact order of constructors in a multiple and/or virtual inheritance situation?
25.15	What is the exact order of destructors in a multiple and/or virtual inheritance situation?

[25.1] How is this section organized?

This section covers a wide spectrum of questions/answers, ranging from the high-level / strategy / design issues, going all the way down to low-level / tactical / programming issues. We cover them in that order.

Please make sure you understand the high-level / strategy / design issues. Too many programmers worry about getting "it" to compile without first deciding whether they really want "it" in the first place. So please read the first several FAQs in this section before worrying about the (important) mechanical details in the last several FAQs.