C++ FAQ Celebrating Twenty-One Years of the C++ FAQ!!!
(Click here for a personal note from Marshall Cline.)
Contents - 40 sections.
[ 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 ]
About the Author.
Marshall Cline
cline@parashift.com
Topical index - 5676 links to 3571 topics.
[ A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z ]
Search the C++ FAQ.
Recent changes - 11 changed FAQs.
In a list, or in a chain, or here: [4.1], [4.2], [6.3], [6.12], [10.3], [15.22], [27.15], [35.13], [35.14], [35.15], [39.6].
Mirrored in 11 countries.
USA, France, Germany, Ireland, Israel, Italy, Poland, Portugal, Spain, Taiwan, U.K..
[31] Reference and value semantics
31.1 What is value and/or reference semantics, and which is best in C++?
31.2 What is "virtual data," and how-can / why-would I use it in C++?
31.3 What's the difference between virtual data and dynamic data?
31.4 Should I normally use pointers to freestore allocated objects for my data members, or should I use "composition"?
31.5 What are relative costs of the 3 performance hits associated with allocating member objects from the freestore?
31.6 Are "inline virtual" member functions ever actually "inlined"?
31.7 Sounds like I should never use reference semantics, right?
31.8 Does the poor performance of reference semantics mean I should pass-by-value?