Design Patterns 5 : Bridge -- Independent variations

最新推荐文章于 2024-10-14 23:59:32 发布

ivanchenhz

最新推荐文章于 2024-10-14 23:59:32 发布

阅读量466

点赞数

分类专栏： Architecture 文章标签： shapes methods idea system

本文链接：https://blog.youkuaiyun.com/ivanchenhz/article/details/6537955

版权

Architecture 专栏收录该内容

7 篇文章

订阅专栏

本文介绍桥接模式在软件设计中的应用。通过分离抽象与实现，使得两者可以独立变化。形状与绘制实例展示了如何通过桥接模式减少冗余并提高代码复用性。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

There are two parts in the system Abstraction (consumer) and Implementation (products), the abstraction part use the implementation part to finish some job, and both the Abstraction and the Implementation are variable.

This is the place the bridge pattern comes to save the world.

The Shape aggregate the Drawing, and has no idea how the Drawing actually do the job.

Meanwhile the Drawing has no idea about the Shape at all.

In this way if we add more shapes or introduce new drawing implementations, it won't affect the other part.

And one more thing, the "One rule, one place" strategy.

In the above design, we add protected methods Shape::drawLine(), Shape::drawCircle(), use them to call the Drawing::drawLine(), Drawing::drawCircle(), instead of calling them directly in XXX::draw().

Which remove redundancy, and encapsulate the Drawing stuff only in Shape class.

Move the commonality upper, and keep the variability lower.