<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: ANTLR By Example: Part 3: Parsing</title>
	<link>http://www.alittlemadness.com/2006/06/19/antlr-by-example-part-3-parsing/</link>
	<description>A man needs a little madness, or else he never dares cut the rope and be free. -Nikos Kazantzakis</description>
	<pubDate>Fri, 21 Nov 2008 00:05:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.1</generator>

	<item>
		<title>By: Bruno Vernay</title>
		<link>http://www.alittlemadness.com/2006/06/19/antlr-by-example-part-3-parsing/#comment-8329</link>
		<author>Bruno Vernay</author>
		<pubDate>Wed, 13 Dec 2006 10:47:34 +0000</pubDate>
		<guid>http://www.alittlemadness.com/2006/06/19/antlr-by-example-part-3-parsing/#comment-8329</guid>
		<description>Very instructive !
I just found that the parser rule's names : orexpression, andexpression, notexpression are missleading. 
I would have understood quicker if they were named : precedence1, precedence2, precedence3 or so

Thanks
Bruno</description>
		<content:encoded><![CDATA[<p>Very instructive !<br />
I just found that the parser rule&#8217;s names : orexpression, andexpression, notexpression are missleading.<br />
I would have understood quicker if they were named : precedence1, precedence2, precedence3 or so</p>
<p>Thanks<br />
Bruno</p>
]]></content:encoded>
	</item>
</channel>
</rss>
