Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Visitor pattern
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== Advantages == Moving operations into visitor classes is beneficial when * many unrelated operations on an object structure are required, * the classes that make up the object structure are known and not expected to change, * new operations need to be added frequently, * an algorithm involves several classes of the object structure, but it is desired to manage it in one single location, * an algorithm needs to work across several independent class hierarchies. A drawback to this pattern, however, is that it makes extensions to the class hierarchy more difficult, as new classes typically require a new <code>visit</code> method to be added to each visitor.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)