CSC/ECE 517 Fall 2012/ch2b 2w51 aa: Difference between revisions

From Expertiza_Wiki
Jump to navigation Jump to search
Line 80: Line 80:
==Conclusion==
==Conclusion==


In search of websites/blogs related to visitor pattern one will realize that very few websites/blogs are available for this design pattern and it appears to be have most narrow use. One can find some sites/discussion forums which debate on whether design pattern like visitor add complexity to the code, one such can be found here [http://programmers.stackexchange.com/questions/48811/what-design-patterns-are-the-worst-or-most-narrowly-defined Programmers Stackexchange]. The definition of this pattern is very clear "separation of algorithms" from an object so as to make later modifications(addition) easy and with no need to change structure of class. The pattern can find good usage in a scenario where the object classes rarely change but one needs to define new operations on the object<ref>[http://en.wikipedia.org/wiki/Visitor_pattern<i>Object Oriented Programming </i>]</ref>.
In search of websites/blogs related to visitor pattern one will realize that very few websites/blogs are available for this design pattern and it appears to be have most narrow use. One can find some sites/discussion forums which debate on whether design pattern like visitor add complexity to the code, one such can be found here [http://programmers.stackexchange.com/questions/48811/what-design-patterns-are-the-worst-or-most-narrowly-defined Programmers Stackexchange]. The definition of this pattern is very clear "separation of algorithms" from an object so as to make later modifications(addition) easy and with no need to change structure of class. The pattern can find good usage in a scenario where the object classes rarely change but one needs to define new operations on the object<ref>[http://en.wikipedia.org/wiki/Visitor_pattern<i>Visitor Pattern </i>]</ref>.


=References=
=References=
<references>
<references>

Revision as of 18:26, 19 November 2012

Visitor Pattern, Directory of sites

The Purpose of this article is to act as a "directory of sites", or a simple quick jump page for the reader. The effort is to try and collect good sources (blog posts, forum chats, general articles etc.) which deal with the Visitor pattern and to make this available to the readers with summary. The readers can then explore the links provided, to understand certain topics that they are interested in. Readers are also encouraged to edit the document in case they are able to contribute good material. Since this is just a quick jump page, there will be an apparent lack of examples. This is in line with the requirements given in the writeup, since we are re-directing you to pages where you will get plenty of information.

Introduction

In Object Oriented Programming <ref>Object Oriented Programming </ref>, the Visitor Pattern is a way of decoupling algorithms to be performed by an object. The way to do this is to create a visitor class which would help to add new virtual function to the classes without modifying their structures. This is accomplished by creating appropriate specializations of the virtual function in visitor class which will take instance reference as input and implement the algorithm using double dispatch.

For more information on the Visitor pattern, you can visit the following links

Motivation

Now that some information is present about what the Visitor pattern is and what it should do, let us explore the motivation behind using the Visitor pattern. Some links are provided for the reader to explore the topic and a brief summary is presented to guide the reader

  • Oodesign One of the top visited sites for design pattern basics , oodesign.com has good introduction, examples and implementation details. Sample code is also available for the reader. The article is good not only from the point of view of explaining the motivation behind Visitor patterns, but also because it follows a good flow in setting up the topic, explanation using examples and concluding with a brief summary
  • SourceMaking This page has good detailed description of visitor pattern and the worth reading part is the discussion section of this page which also talks about how double dispatch is related to visitor.
  • DoFactory Simple introductory page which describes and talks about the pattern in short. It is a very 'bare-bones' reference article, but is a good introductory piece

Visitor Pattern in Java

  • DZone The article explains the use of the Visitor pattern in Java. A real world analogy is given initially and then Java implementation of a Visitor pattern is explained. The author maintains a good flow and then concludes with a mention of few disadvantages of the pattern.
  • JavaWorld This article provides a very detailed example of a Visitor pattern implementation in Java. The author guides the reader through each step, explaining the process as he goes along.
  • Snehaprashant Blogspot The article starts of by providing a brief description of the pattern, it's advantages and disadvantages and then provides a detailed example of the Visitor pattern. The flow is good and the code example is good, but the explanation of the code is not provided. However the code is quite self explanatory.

Drawback

1. Snehaprashant Blogspot does not provide explanation of the code example.

Visitor Pattern in C++

Following are the links which provide examples based on C++:

  • SourceMaking Example 1 A comparison is provided between the 'before' and 'after' code based on the Visitor pattern implementation. This link and the next couple of links are part of the same discussion provided in SourceMaking.
  • SourceMaking Example 2
  • SourceMaking Example 3
  • Software Engineering group This page explains visitor pattern in detail from the basics till implementation using C++. It has implementation details and also discusses issues that could possibly arise when using the Visitor pattern. This page provides good code example in C++ along with detailed explanation. This page overcomes the drawback of SourceMaking.

Drawback

1. Good code in SourceMaking but lack of proper explanations to the code. If the reader has no prior knowledge about visitor pattern then it is difficult to understand this code.

Visitor Pattern in Python

Following are two links which provide good examples of implementation of visitor patterns in python:

  • Lamby Blog The author sets up the explanation by using the example of an Abstract syntax tree traversal. A brief comparison is also provided about the differences in a Java implementation and a Python implementation for the same.
  • Curtis The author presents a similar example as the link before.

Drawback

1. Lamby Blog is not well organized and no detailed discussion about the code he provided.

2. A point to note about Curtis is that there is sufficient amount of code, but not enough explanation. However, the code is still useful with prior knowledge of visitor pattern.

Visitor Pattern in Ruby

Following are the links which provide examples based on Ruby

  • Scribd This link provides a good discussion about all design patterns including the Visitor pattern. Implementation is done in Ruby and there are sufficient code examples.
  • Gist Github This link provides a singular example of Ruby implementation of the Visitor pattern.

Drawback

1. In Gist Github only code is available and no explanation is provided because of nature of the site.

Advantages

  • UCLA CS helps to understand the advantage of a design pattern like visitor, which are the features it combines and how it makes it easy for programmer to implement those ideas.

Disadvantages

  • DeveloperFusionhas a subsection in the visitor pattern section which discusses issues related to visitor pattern.
  • Oodesign describes issues with visitor pattern in section Specific problems and implementation.

Conclusion

In search of websites/blogs related to visitor pattern one will realize that very few websites/blogs are available for this design pattern and it appears to be have most narrow use. One can find some sites/discussion forums which debate on whether design pattern like visitor add complexity to the code, one such can be found here Programmers Stackexchange. The definition of this pattern is very clear "separation of algorithms" from an object so as to make later modifications(addition) easy and with no need to change structure of class. The pattern can find good usage in a scenario where the object classes rarely change but one needs to define new operations on the object<ref>Visitor Pattern </ref>.

References

<references>