Abstract
One very common situation that occurs when designing software is the so-called State space explosion where the number of related entities required to represent all possible states “explodes” in a Cartesian product fashion. For example, if you have circles and squares of different colors, you might end up with classes such as RedSquare/BlueSquare/RedCircle/BlueCircle and so on. Clearly nobody wants that.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Change history
30 April 2021
The original version of the chapters 5, 6 & 8 was inadvertently published with the introductory text placed at the end of incorrect chapters. The chapters affected are:
Notes
- 1.
I am being sly here by using a calling convention. This is done purely for illustration purposes. If every rendered shape shares neither parent nor child of another shape, you can simplify this by making a series of similarly named overloads, that is, Render(Circle c), Render(Square s), and so on. The choice is up to you.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2020 Dmitri Nesteruk
About this chapter
Cite this chapter
Nesteruk, D. (2020). Bridge. In: Design Patterns in .NET Core 3. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-6180-4_8
Download citation
DOI: https://doi.org/10.1007/978-1-4842-6180-4_8
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-6179-8
Online ISBN: 978-1-4842-6180-4
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)