tag:blogger.com,1999:blog-882821950355432699.post4651732284954721789..comments2009-11-10T08:23:18.611+11:00Paulhttp://www.blogger.com/profile/18224234643439645641noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-882821950355432699.post-84551267751011322222009-11-10T08:23:18.611+11:002009-11-10T08:23:18.611+11:00Sure. In this case the algorithm is the introducer. I don&#39;t follow your point about the Foo and Bar classes having dependencies though.Paulhttp://www.blogger.com/profile/18224234643439645641noreply@blogger.comtag:blogger.com,1999:blog-882821950355432699.post-60722044968362294652009-11-09T21:49:16.448+11:002009-11-09T21:49:16.448+11:00Visitor is made to separe algorithm from original object.<br />For instance, you may have your entities and a visitor to play a sound matching the entity. You don&#39;t want a call to the sound library in your entity so you put it in a visitor.<br />Moreover your classes Foo and Bar have dependancies which is not always a good thing.Guillaumenoreply@blogger.comtag:blogger.com,1999:blog-882821950355432699.post-79237062228321339182008-11-03T17:45:00.000+11:002008-11-03T17:45:00.000+11:00Good.Andrew Moylanhttp://www.blogger.com/profile/15277166449214446604noreply@blogger.com