C Programming FAQs: Frequently Asked Questions - page 1
- FAQ 5.11 What are the advantages of polymorphism and dynamic binding?
- FAQ 5.12 How does OO help produce flexible and extensible software?
- FAQ 5.13 How can old code call new code?
- FAQ 5.14 What is an abstraction and why is it important?
- FAQ 5.15 Should abstractions be user-centric or developer-centric?
- FAQ 5.16 What s the difference between encapsulation and abstraction?
- FAQ 5.17 What are the consequences of encapsulating a bad abstraction?
- FAQ 5.18 What s the value of separating interface from implementation?
- FAQ 5.19 How can separating interface from implementation improve performance as well as flexibility?
- FAQ 5.20 What is the best way to create a good interface to an abstraction?
- FAQ 5.21 How are getset member functions related to poorly designed interfaces?
- FAQ 5.22 Should there be a get and a set member function for each member datum?
- FAQ 5.23 Is the real purpose of a class to export data?
- FAQ 5.24 Should OO be viewed as data-centric?
- Chapter 6. Specification of Observable Behavior
- FAQ 6.01 What is the purpose of this chapter?
- FAQ 6.02 Should users of a member function rely on what the code actually does or on the specification?
- FAQ 6.03 What are the advantages of relying on the specification rather than the implementation?
- FAQ 6.04 What are advertised requirements and advertised promises?
- FAQ 6.05 How are the advertised requirements and advertised promises of the member functions specified?
- FAQ 6.06 Why are changes feared in development organizations that don t use specification?
- FAQ 6.07 How do developers determine if a proposed change will break existing code?
- FAQ 6.08 What are the properties of a substitutable (backward compatible) change in a specification?
- FAQ 6.09 How can it be shown that the implementation of a member function fulfills its specification?
- FAQ 6.10 Is it possible to keep the specification synchronized with the code?
- Chapter 7. Proper Inheritance
- FAQ 7.01 What is proper inheritance?
- FAQ 7.02 What are the benefits of proper inheritance?
- FAQ 7.03 What is improper inheritance?
- FAQ 7.04 Isn t the difference between proper and improper inheritance obvious?
- FAQ 7.05 Is substitutability based on what the code does or what the specification promises the code will do?
- FAQ 7.06 Is it proper to revoke (hide) an inherited public: member function?
- FAQ 7.07 What is specialization?
- FAQ 7.08 What do subsets have to do with proper inheritance?
- Chapter 8. Detecting and Correcting Improper Inheritance
- FAQ 8.01 Can improper inheritance wreck a project?
- FAQ 8.02 What s the best way to learn how to avoid improper inheritance?
- FAQ 8.03 Is intuition a reliable guide to understanding proper inheritance?
- FAQ 8.04 Is an Ostrich a kind-of Bird ?
- FAQ 8.05 Should an overridden virtual function throw an exception?
- FAQ 8.06 Can an overridden virtual function be a no-op?
- FAQ 8.07 Why does C make it so hard to fix the OstrichBird dilemma?
- FAQ 8.08 Should Circle inherit from Ellipse ?
- FAQ 8.09 What can be done about the asymmetric-circle dilemma?
- FAQ 8.10 What is the one issue in these FAQs that doesn t seem to die?
- FAQ 8.11 Should Stack inherit from List ?
- FAQ 8.12 Is code reuse the main purpose of inheritance?
- FAQ 8.13 Is container-of-thing a kind-of container-of-anything?
- FAQ 8.14 Is bag-of-apple a kind-of bag-of-fruit, assuming bag-of-fruit allows the insertion of any kind-of fruit?
- FAQ 8.15 Is parking-lot-for-cars a kind-of parking-lot-for-arbitrary-vehicles (assuming parking-lot-for-vehicles allows parking any kind-of vehicle)?
- FAQ 8.16 Is array-of Derived a kind-of array-of Base ?
- FAQ 8.17 Does the fact that an array-of Derived can be passed as an array-of Base mean that arrays are bad?
- Chapter 9. Error Handling Strategies
- FAQ 9.01 Is error handling a major source of fundamental mistakes?
- FAQ 9.02 How should runtime errors be handled in C?
- FAQ 9.03 What happens to objects in stack frames that become unwound during the throw catch process?
- FAQ 9.04 What is an exception specification?
- FAQ 9.05 What are the disadvantages of using return codes for error handling?
- FAQ 9.06 What are the advantages of throw ... catch ?
- FAQ 9.07 Why is it helpful to separate normal logic from exception handling logic?
- FAQ 9.08 What is the hardest part of using exception handling?
- FAQ 9.09 When should a function throw an exception?
- FAQ 9.10 What is the best approach for the hierarchy of exception objects?
- FAQ 9.11 How should exception classes be named?
- FAQ 9.12 Where do setjmp and longjmp belong in C?
- Chapter 10. Testing Strategies
- FAQ 10.01 What is the purpose of this chapter?
- FAQ 10.02 What are the advantages of self-testing objects?
- FAQ 10.03 What are some common excuses people use for not building self-testing into their objects?
- FAQ 10.04 What will happen if techniques like those presented here are not used?
- FAQ 10.05 When is a class correct?
- FAQ 10.06 What is behavioral self-testing?
- FAQ 10.07 What is a class invariant?
- FAQ 10.08 Why should the invariant be captured explicitly?
- FAQ 10.09 When should the testInvariant() member function be called?
- FAQ 10.10 What can be done to ensure that an object doesn t get blown away by a wild pointer?
- Part III: Language Facilities
- Chapter 11. References
- FAQ 11.01 What is a reference?
- FAQ 11.02 What does referent mean?
