<?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"
	>
<channel>
	<title>Comments on: Object Teams rocks :)</title>
	<atom:link href="http://blog.objectteams.org/2010/08/object-teams-rocks/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.objectteams.org/2010/08/object-teams-rocks/</link>
	<description>Everthing Object Teams - adding team spirit to your objects.</description>
	<pubDate>Fri, 18 May 2012 09:14:46 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: stephan</title>
		<link>http://blog.objectteams.org/2010/08/object-teams-rocks/#comment-2341</link>
		<dc:creator>stephan</dc:creator>
		<pubDate>Fri, 20 Aug 2010 19:12:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.objectteams.org/?p=58#comment-2341</guid>
		<description>@Nicolas: Sure do I know Scala, and sure did I not invent class linearization. I can't remember if I talked about this with Martin Odersky. I learned many cool things about inheritance from Erik Ernst, and I know Erik and Martin are very well informed about each other's contributions. So it's a community of language designers whose ideas actually converge in some topics, which is indeed a nice place to be at.

Next question might be: how are inheritance hierarchies visualized in the Scala IDE? I haven't checked.

Next question might be: how did they implement their hierarchy view (if they have one), but that wouldn't be an even comparison, because the Scala IDE is green field development, whereas the Object Teams Development Tooling started from the full blown JDT :)</description>
		<content:encoded><![CDATA[<p>@Nicolas: Sure do I know Scala, and sure did I not invent class linearization. I can&#8217;t remember if I talked about this with Martin Odersky. I learned many cool things about inheritance from Erik Ernst, and I know Erik and Martin are very well informed about each other&#8217;s contributions. So it&#8217;s a community of language designers whose ideas actually converge in some topics, which is indeed a nice place to be at.</p>
<p>Next question might be: how are inheritance hierarchies visualized in the Scala IDE? I haven&#8217;t checked.</p>
<p>Next question might be: how did they implement their hierarchy view (if they have one), but that wouldn&#8217;t be an even comparison, because the Scala IDE is green field development, whereas the Object Teams Development Tooling started from the full blown JDT <img src='http://blog.objectteams.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nicolas Lalevée</title>
		<link>http://blog.objectteams.org/2010/08/object-teams-rocks/#comment-2338</link>
		<dc:creator>Nicolas Lalevée</dc:creator>
		<pubDate>Fri, 20 Aug 2010 16:30:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.objectteams.org/?p=58#comment-2338</guid>
		<description>I don't know if you know Scala, but linearization is exactly what this language uses to compute the type hierarchy of classes that extends many traits. Your solution is definitively the right one ! :)</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know if you know Scala, but linearization is exactly what this language uses to compute the type hierarchy of classes that extends many traits. Your solution is definitively the right one ! <img src='http://blog.objectteams.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
</channel>
</rss>

