We wrap up the season with the observer pattern and a review of what we have learned.  This pattern is one that you probably have already encountered.  Instead of an observer, you probably have heard it called a listener. The Observer Pattern Defined As always, we will start with the “Gang of Four” intent to set the stage for our discussion. “Define a one-to-many dependency between objects so that when one object changes state, all its dependents are notified and updated automatically.” Thus, the observer pattern is precisely what the name implies.  You assign an object to an observer, and when something changes in the observed object, the observer is notified.  The key to this is that it is a one-to-many... Read more

The visitor pattern is the last of the behavioral ones for us to review.  This is going to feel similar to some others that allow us to abstract functionality such as a command.  This one provides us with a way to group functionality and avoids duplication or even sprawl of our code. The Visitor Pattern Defined As always, we will start with the “Gang of Four” intent to set the stage for our discussion. “Represent an operation to be perfomed on the elements of an object structure. Visitor lets you define a new operation without changing the classes of the elements on which it operates.” Simply put, this pattern allows us to abstract and group functions that we will be performed on... Read more