<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Live patterns: Switching to the visitor design pattern</title>
	<atom:link href="http://www.davidrabinowitz.com/en/2009/05/29/live-patterns-switching-to-the-visitor-design-pattern/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.davidrabinowitz.com/en/2009/05/29/live-patterns-switching-to-the-visitor-design-pattern/</link>
	<description>From the trenches of Java development</description>
	<lastBuildDate>Mon, 04 Jan 2010 11:20:38 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dimitris Andreou</title>
		<link>http://www.davidrabinowitz.com/en/2009/05/29/live-patterns-switching-to-the-visitor-design-pattern/comment-page-1/#comment-30</link>
		<dc:creator>Dimitris Andreou</dc:creator>
		<pubDate>Sat, 30 May 2009 19:26:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidrabinowitz.com/en/?p=31#comment-30</guid>
		<description>Well, I don&#039;t think this is the life-saver you seem to be describing...

What visitor buys you here is merely the fact that you don&#039;t have to put an abstract method plus implementations for each distinct type-based desicion (bloating a single file), but create those implementations externally (out of the itinerary source files). I.e. you just managed to avoid putting the type-based code in the types themselves, but somewhere else. Good for you. Where would we be without patterns! :)

Btw, Scala supports the switch you describe (where the compiler notifies you of missed cases).</description>
		<content:encoded><![CDATA[<p>Well, I don&#8217;t think this is the life-saver you seem to be describing&#8230;</p>
<p>What visitor buys you here is merely the fact that you don&#8217;t have to put an abstract method plus implementations for each distinct type-based desicion (bloating a single file), but create those implementations externally (out of the itinerary source files). I.e. you just managed to avoid putting the type-based code in the types themselves, but somewhere else. Good for you. Where would we be without patterns! <img src='http://www.davidrabinowitz.com/en/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Btw, Scala supports the switch you describe (where the compiler notifies you of missed cases).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Omar</title>
		<link>http://www.davidrabinowitz.com/en/2009/05/29/live-patterns-switching-to-the-visitor-design-pattern/comment-page-1/#comment-29</link>
		<dc:creator>Omar</dc:creator>
		<pubDate>Sat, 30 May 2009 16:09:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidrabinowitz.com/en/?p=31#comment-29</guid>
		<description>Ok, I think you make your point about how much cumbersome could be the code with the first two sniplets. Could you please ilustrate the visitor design patter with an example of your own? The link in the wikipedia it&#039;s ok, but don&#039;t be cheap and complete your post. ;)</description>
		<content:encoded><![CDATA[<p>Ok, I think you make your point about how much cumbersome could be the code with the first two sniplets. Could you please ilustrate the visitor design patter with an example of your own? The link in the wikipedia it&#8217;s ok, but don&#8217;t be cheap and complete your post. <img src='http://www.davidrabinowitz.com/en/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
