info/DesignPatternsPHP
1
0
Fork 0
mirror of https://github.com/DesignPatternsPHP/DesignPatternsPHP.git synced 2025-08-05 06:27:25 +02:00
Code Issues Projects Releases Wiki Activity

Merge pull request #109 from Bilge/patch-2

Browse Source 
Copy edit for NullObject readme
This commit is contained in:
Dominik Liebler
2014-11-05 18:03:57 +01:00
parent 37cdbd6c23 b71b988fc0
commit fc55b9b336
1 changed files with 6 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
Behavioral/NullObject/README.md
View File

@@ -2,15 +2,13 @@
## Purpose
NullOutput is a example of NullObject pattern. It is not formally a Design Pattern by the GoF but it's a schema which appears frequently enough to
be a pattern. Furthermore it is a really good pattern in my opinion:
NullObject is not a GoF design pattern but a schema which appears frequently enough to be considered a pattern. It has the following benefits:
* the code in the client is simple
* it reduces the chance of null pointer exception
* less "if" => less test cases
* Client code is simplified
* Reduces the chance of null pointer exceptions
* Fewer conditionals require less test cases
Every time you have a method which returns an object or null, you should return an object or a `NullObject`. With NullObject, you don't need
a statement like `if (!is_null($obj)) { $obj->callSomething(); }` anymore.
Methods that return an object or null should instead return an object or `NullObject`. `NullObject`s simplify boilerplate code such as `if (!is_null($obj)) { $obj->callSomething(); }` to just `$obj->callSomething();` by eliminating the conditional check in client code.
## Examples
@@ -21,4 +19,4 @@ a statement like `if (!is_null($obj)) { $obj->callSomething(); }` anymore.
## UML Diagram
![Alt NullObject UML Diagram](uml/uml.png)
![Alt NullObject UML Diagram](uml/uml.png)