Summary
We have started “thinking OOP.” We talked about how verification is complex, and how this complexity must be managed. We talked about the goal of creating flexible, adaptable code, and how achieving this goal may complicate the code.
We got into coding a bit by talking about the separation between interface and implementation. We also touched on the subject of base classes and the different ways they can be used.
Keywords
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.
NOBODY expects the Spanish Inquisition! Amongst our weaponry are such diverse elements as fear, surprise, ruthless efficiency, an almost fanatical devotion to the Pope, and nice red uniforms-Oh damn! Monty Python, episode 15, 1970
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsPreview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2006 Springer Science+Business Media, LLC
About this chapter
Cite this chapter
(2006). Thinking OOP. In: Hardware Verification with C++. Springer, Boston, MA. https://doi.org/10.1007/978-0-387-36254-0_9
Download citation
DOI: https://doi.org/10.1007/978-0-387-36254-0_9
Publisher Name: Springer, Boston, MA
Print ISBN: 978-0-387-25543-9
Online ISBN: 978-0-387-36254-0
eBook Packages: EngineeringEngineering (R0)