State
Aside from potentially improving separation of concerns, the visitor pattern has an additional advantage over simply calling a polymorphic method: a visitor object can have state. This is extremely useful in many cases where the action performed on the object depends on previous such actions.
An example of this is a pretty-printer in a programming language implementation (such as a compiler or interpreter). Such a pretty-printer object (implemented as a visitor, in this example), will visit nodes in a data structure that represents a parsed and processed program. The pretty-printer will then generate a textual representation of the program tree. To make the representation human-readable, the pretty-printer should properly indent program statements and expressions. The current indentation level can then be tracked by the visitor as its state, correctly applying encapsulation, whereas in a simple polymorphic method invocation, the indentation level would have to be exposed as a parameter and the caller would rely on the method implementation to use and propagate this parameter correctly.
Read more about this topic: Visitor Pattern
Famous quotes containing the word state:
“Alas, why would you heap this care on me?
I am unfit for state and majesty.
I do beseech you take it not amiss,
I cannot nor I will not yield to you.”
—William Shakespeare (1564–1616)
“And now the end is near
And so I face the final curtain,
I’ll state my case of which I’m certain.
I’ve lived a life that’s full, I traveled each and ev’ry highway,
And more, much more than this. I did it my way.”
—Frank Sinatra (b. 1915)
“The Apache have a legend that the coyote brought them fire and that the bear in his hibernations communes with the spirits of the “overworld” and later imparts the wisdom gained thereby to the medicine men.”
—Administration in the State of Arizona, U.S. public relief program (1935-1943)