<?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: The YARD Roadmap to 1.0</title>
	<atom:link href="http://gnuu.org/2008/02/22/the-yard-roadmap-to-10/feed/" rel="self" type="application/rss+xml" />
	<link>http://gnuu.org/2008/02/22/the-yard-roadmap-to-10/</link>
	<description>my word against yours, fight.</description>
	<lastBuildDate>Thu, 29 Jul 2010 07:40:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: gnuu.org: YARD Milkshakes (0.2.3) Released</title>
		<link>http://gnuu.org/2008/02/22/the-yard-roadmap-to-10/comment-page-1/#comment-172</link>
		<dc:creator>gnuu.org: YARD Milkshakes (0.2.3) Released</dc:creator>
		<pubDate>Sun, 07 Jun 2009 23:49:10 +0000</pubDate>
		<guid isPermaLink="false">http://gnuu.org/2008/02/22/the-yard-roadmap-to-10/#comment-172</guid>
		<description>[...] important. The parser was something that was on the table for a long time, dating back to my first roadmap to 1.0 post last year. Now that it’s complete, we can start looking ahead. As more of the groundwork is [...]</description>
		<content:encoded><![CDATA[<p>[...] important. The parser was something that was on the table for a long time, dating back to my first roadmap to 1.0 post last year. Now that it’s complete, we can start looking ahead. As more of the groundwork is [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Loren Segal</title>
		<link>http://gnuu.org/2008/02/22/the-yard-roadmap-to-10/comment-page-1/#comment-135</link>
		<dc:creator>Loren Segal</dc:creator>
		<pubDate>Thu, 05 Feb 2009 21:33:45 +0000</pubDate>
		<guid isPermaLink="false">http://gnuu.org/2008/02/22/the-yard-roadmap-to-10/#comment-135</guid>
		<description>Hi Joshua,

This post was written a while ago. YARD is now far more stable as far as parsing goes, though it&#039;s still not perfect. That said, YARD has been able to parse through Rails for the longest time now, so that should say something about its abilities. I&#039;m actually currently working on a revamp of the parser for 1.9 on (using Ripper supplied with Ruby 1.9) that should improve both speed and reliability even more.</description>
		<content:encoded><![CDATA[<p>Hi Joshua,</p>
<p>This post was written a while ago. YARD is now far more stable as far as parsing goes, though it&#8217;s still not perfect. That said, YARD has been able to parse through Rails for the longest time now, so that should say something about its abilities. I&#8217;m actually currently working on a revamp of the parser for 1.9 on (using Ripper supplied with Ruby 1.9) that should improve both speed and reliability even more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joshua Go</title>
		<link>http://gnuu.org/2008/02/22/the-yard-roadmap-to-10/comment-page-1/#comment-134</link>
		<dc:creator>Joshua Go</dc:creator>
		<pubDate>Thu, 05 Feb 2009 07:18:49 +0000</pubDate>
		<guid isPermaLink="false">http://gnuu.org/2008/02/22/the-yard-roadmap-to-10/#comment-134</guid>
		<description>Hi Loren. I was looking at Merb and their use of Yard, and what caught my attention was how you could formally declare expected types of variables that you pass in. This is not available in RDoc, as far as I can tell and have seen so far. Is the parsing really a mess as you imply in many of your other posts? That might make people hesitant to use it, whereas I&#039;m pretty happy with what it can do so far.</description>
		<content:encoded><![CDATA[<p>Hi Loren. I was looking at Merb and their use of Yard, and what caught my attention was how you could formally declare expected types of variables that you pass in. This is not available in RDoc, as far as I can tell and have seen so far. Is the parsing really a mess as you imply in many of your other posts? That might make people hesitant to use it, whereas I&#8217;m pretty happy with what it can do so far.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
