<?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: GLR parsing is the future</title>
	<atom:link href="http://shape-of-code.coding-guidelines.com/2009/08/27/glr-parsing-is-the-future/feed/" rel="self" type="application/rss+xml" />
	<link>http://shape-of-code.coding-guidelines.com/2009/08/27/glr-parsing-is-the-future/</link>
	<description></description>
	<lastBuildDate>Sun, 12 Feb 2012 22:01:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: The Shape of Code &#187; Parsing Fortran 95</title>
		<link>http://shape-of-code.coding-guidelines.com/2009/08/27/glr-parsing-is-the-future/comment-page-1/#comment-874</link>
		<dc:creator>The Shape of Code &#187; Parsing Fortran 95</dc:creator>
		<pubDate>Wed, 23 Dec 2009 02:25:47 +0000</pubDate>
		<guid isPermaLink="false">http://shape-of-code.coding-guidelines.com/?p=113#comment-874</guid>
		<description>[...] conflicts and 1 reduce/reduce conflict. These conflicts looked like they could all be handled using glr parsing. The grammar contained 922 productions, somewhat large but I was only interested in actively making [...]</description>
		<content:encoded><![CDATA[<p>[...] conflicts and 1 reduce/reduce conflict. These conflicts looked like they could all be handled using glr parsing. The grammar contained 922 productions, somewhat large but I was only interested in actively making [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

