The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →The Visitor design pattern separates operations from the classes those operations work on. It is useful when the set of element types is relatively stable but new operations are likely; it is a poor fit when the element hierarchy changes often. Its defining mechanism is the collaboration between an element’s accept(visitor) method and a type-specific visitor method—not simply walking a tree.
What is the Visitor design pattern?
Visitor represents an operation separately from the object-structure elements on which it operates. In the conventional form, each element accepts a visitor, and the visitor implements the operation for the supported element types. This lets you add an operation without placing its logic in every element class. [PMI Disciplined Agile]
As an Amazon Associate I earn from qualifying purchases.
The Gang of Four intent, as quoted by PMI Disciplined Agile, is: “Represent an operation to be performed 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.”
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →How does Visitor work, and why is it called double dispatch?
An element exposes an accept(visitor) method. Each concrete element implements that method by passing itself to the visitor method for its own type. For example, a circle calls visitor.visitCircle(this), while a square calls visitor.visitSquare(this). A concrete visitor supplies the behavior for each supported element type. [GoF Pattern]
#1 Best Overall
The operation therefore depends on two concrete types: the element and the visitor. This is commonly called double dispatch. The element’s implementation selects the matching visitor method, and that method belongs to the concrete visitor that defines the desired operation. [PHPatterns]
For example, a document model might contain paragraphs and images. A plain-text export visitor can define what to do with each type; a statistics visitor can count them or collect other information. Both operations work over the same element classes, while their logic remains in separate visitor classes.
Rank #2
Walking a document tree may be part of applying a visitor, but traversal alone is not the pattern. The essential mechanism is the accept call and the type-specific visit method.
When should you use the Visitor pattern?
Use Visitor when element types are fairly stable and you expect to add multiple operations over them. Each new visitor can keep one operation’s logic together instead of spreading it through the element classes. [PMI Disciplined Agile]
Before choosing it, consider which changes your design needs to make easy:
| Likely change | Visitor’s effect |
|---|---|
| Adding an operation | Usually straightforward: add a visitor that implements the operation for the supported element types. |
| Adding an element type | Usually more involved: the visitor contract and concrete visitors may need a method or other update for the new type. [PHPatterns] |
| Keeping behavior with each element | Ordinary methods may be simpler when the behavior naturally belongs to an element and is not expected to vary independently. |
| Keeping one operation’s logic together | A visitor can make that operation easier to locate and change across several element types. |
Also consider ownership and cohesion: a visitor is useful when an operation forms a coherent unit that should change independently, but it can feel awkward if the behavior belongs naturally inside each element.
Rank #4
What are the disadvantages of the Visitor pattern?
- New element types are costly. The visitor interface represents the element types it supports. Introducing a new type can require changing that contract and updating concrete visitors. [PHPatterns]
- It couples visitors to the structure. Visitor methods name or otherwise account for element types, so changes to the element hierarchy ripple into visitor code. [PMI Disciplined Agile]
- It adds indirection. The element-to-visitor call makes the flow less direct than invoking a method on the element or using a straightforward conditional. [w3sDesign]
- It may duplicate visitor structure. Each concrete visitor must account for the supported element types, even when some cases need little or no work.
These are maintenance and design costs; they do not establish a universal runtime-performance penalty. No general performance conclusion follows without measurements for a particular implementation.
Free tools Windows power users keep installed
One-click scans. No signup required.
What alternatives should you consider?
If there are only a few operations, or the element types change frequently, a method on each element or a simple conditional may be easier to maintain. If the language provides algebraic data types, pattern matching, or native multiple dispatch, compare those features with Visitor: they may express the same operation with less ceremony, depending on the language and how the model evolves.
Visitor is not automatically better because a program has a hierarchy or a tree. Choose it when separating operations from a stable set of element types solves a real change-management problem; otherwise, prefer the simpler design.
Further reading
The canonical pattern appears in Design Patterns: Elements of Reusable Object-Oriented Software, the Gang of Four book identified as the source of the pattern’s intent. [PMI Disciplined Agile]
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
