gaspersic/java-design-patterns
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Work towards #56: Add permalink to every pattern

Browse Source 
This makes cleaner URLs thanks to jekyll
This commit is contained in:
Markus
2015-08-15 18:03:05 +02:00
parent fbb12b53ba
commit fdb9be1e76
57 changed files with 113 additions and 80 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
bridge/index.md
View File

@ -2,6 +2,7 @@
layout: pattern
title: Bridge
folder: bridge
permalink: /patterns/bridge/
categories: pattern_cat
tags: pattern_tag
---
@ -18,4 +19,4 @@ vary independently.
* both the abstractions and their implementations should be extensible by subclassing. In this case, the Bridge pattern lets you combine the different abstractions and implementations and extend them independently
* changes in the implementation of an abstraction should have no impact on clients; that is, their code should not have to be recompiled.
* you have a proliferation of classes. Such a class hierarchy indicates the need for splitting an object into two parts. Rumbaugh uses the term "nested generalizations" to refer to such class hierarchies
* you want to share an implementation among multiple objects (perhaps using reference counting), and this fact should be hidden from the client. A simple example is Coplien's String class, in which multiple objects can share the same string representation.
* you want to share an implementation among multiple objects (perhaps using reference counting), and this fact should be hidden from the client. A simple example is Coplien's String class, in which multiple objects can share the same string representation.