mirror of
https://github.com/JakubVojvoda/design-patterns-cpp.git
synced 2025-12-17 12:54:36 +03:00
update READMEs
This commit is contained in:
@@ -1,7 +1,7 @@
|
||||
## Bridge
|
||||
|
||||
Decouple an abstraction from its implementation so that the two can
|
||||
vary independently.
|
||||
Decouple an abstraction from its implementation so that the two can vary independently.
|
||||
Bridge pattern has structural purpose and applies to objects, so it deals with the composition of objects.
|
||||
|
||||
### When to use
|
||||
|
||||
|
||||
10
composite/README.md
Normal file
10
composite/README.md
Normal file
@@ -0,0 +1,10 @@
|
||||
## Composite
|
||||
|
||||
Compose objects into tree structures to represent part-whole hierarchies.
|
||||
Composite lets clients treat individual objects and compositions of objects uniformly.
|
||||
The pattern has structural purpose and applies to objects.
|
||||
|
||||
### When to use
|
||||
|
||||
* you want to represent part-whole hierarchies of objects
|
||||
* you want clients to be able to ignore the difference between compositions of objects and individual objects
|
||||
11
decorator/README.md
Normal file
11
decorator/README.md
Normal file
@@ -0,0 +1,11 @@
|
||||
## Decorator
|
||||
|
||||
Attach additional responsibilities to an object dynamically. Decorators
|
||||
provide a flexible alternative to subclassing for extending functionality.
|
||||
The pattern has structural purpose and applies to objects.
|
||||
|
||||
### When to use
|
||||
|
||||
* to add responsibilities to individual objects dynamically and transparently, that is, without affecting other objects
|
||||
* for responsibilities that can be withdrawn
|
||||
* when extension by subclassing is impractical
|
||||
Reference in New Issue
Block a user