<?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: A simple lexer in Python</title>
	<atom:link href="http://www.gooli.org/blog/a-simple-lexer-in-python/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gooli.org/blog/a-simple-lexer-in-python/</link>
	<description>on software development and related issues</description>
	<lastBuildDate>Tue, 29 Nov 2011 07:10:01 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: lastindex</title>
		<link>http://www.gooli.org/blog/a-simple-lexer-in-python/#comment-18619</link>
		<dc:creator>lastindex</dc:creator>
		<pubDate>Mon, 22 Mar 2010 12:18:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.gooli.org/blog/a-simple-lexer-in-python/#comment-18619</guid>
		<description>[...] Ramblings Jasper Potts&#039;s Blog is proudly powered by WordPress. Entries (RSS) and Comments (RSS) ...gooli.org A simple lexer in PythonI&#039;m taking a course on building compilers at the Israeli Open University and just learned ... to my [...]</description>
		<content:encoded><![CDATA[<p>[...] Ramblings Jasper Potts&#39;s Blog is proudly powered by WordPress. Entries (RSS) and Comments (RSS) &#8230;gooli.org A simple lexer in PythonI&#39;m taking a course on building compilers at the Israeli Open University and just learned &#8230; to my [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcin</title>
		<link>http://www.gooli.org/blog/a-simple-lexer-in-python/#comment-16653</link>
		<dc:creator>Marcin</dc:creator>
		<pubDate>Fri, 08 Jan 2010 20:58:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.gooli.org/blog/a-simple-lexer-in-python/#comment-16653</guid>
		<description>I like your trick of creating this one humongous ORed regexp that combines all of the other expressions. I don&#039;t think it generalizes very well for very complicated regexps (i.e. regexps that contain ORs in them), but still it&#039;s pretty neat.</description>
		<content:encoded><![CDATA[<p>I like your trick of creating this one humongous ORed regexp that combines all of the other expressions. I don&#8217;t think it generalizes very well for very complicated regexps (i.e. regexps that contain ORs in them), but still it&#8217;s pretty neat.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William</title>
		<link>http://www.gooli.org/blog/a-simple-lexer-in-python/#comment-7687</link>
		<dc:creator>William</dc:creator>
		<pubDate>Wed, 28 Jan 2009 06:53:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.gooli.org/blog/a-simple-lexer-in-python/#comment-7687</guid>
		<description>Nice idea, well presented.  A good example also of using the &quot;yield&quot; statement.</description>
		<content:encoded><![CDATA[<p>Nice idea, well presented.  A good example also of using the &#8220;yield&#8221; statement.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Evan</title>
		<link>http://www.gooli.org/blog/a-simple-lexer-in-python/#comment-7480</link>
		<dc:creator>Evan</dc:creator>
		<pubDate>Mon, 05 Jan 2009 08:34:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.gooli.org/blog/a-simple-lexer-in-python/#comment-7480</guid>
		<description>Wow, very neat. I&#039;ll be using what you&#039;ve shown here in future projects. Maybe a template parser.

You structured this article very well, by the way.</description>
		<content:encoded><![CDATA[<p>Wow, very neat. I&#8217;ll be using what you&#8217;ve shown here in future projects. Maybe a template parser.</p>
<p>You structured this article very well, by the way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FÄ±rat KÃœÃ‡ÃœK</title>
		<link>http://www.gooli.org/blog/a-simple-lexer-in-python/#comment-2143</link>
		<dc:creator>FÄ±rat KÃœÃ‡ÃœK</dc:creator>
		<pubDate>Tue, 22 Jan 2008 21:04:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.gooli.org/blog/a-simple-lexer-in-python/#comment-2143</guid>
		<description>good design. congratulations.</description>
		<content:encoded><![CDATA[<p>good design. congratulations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gooli</title>
		<link>http://www.gooli.org/blog/a-simple-lexer-in-python/#comment-1813</link>
		<dc:creator>gooli</dc:creator>
		<pubDate>Mon, 03 Dec 2007 12:45:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.gooli.org/blog/a-simple-lexer-in-python/#comment-1813</guid>
		<description>I am, but apparently it is only suitable for lexing languages that are similar to shell scripts.</description>
		<content:encoded><![CDATA[<p>I am, but apparently it is only suitable for lexing languages that are similar to shell scripts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Norbert Klamann</title>
		<link>http://www.gooli.org/blog/a-simple-lexer-in-python/#comment-1812</link>
		<dc:creator>Norbert Klamann</dc:creator>
		<pubDate>Mon, 03 Dec 2007 12:08:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.gooli.org/blog/a-simple-lexer-in-python/#comment-1812</guid>
		<description>Are you aware of the &#039;shlex&#039; module ?</description>
		<content:encoded><![CDATA[<p>Are you aware of the &#8217;shlex&#8217; module ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gooli</title>
		<link>http://www.gooli.org/blog/a-simple-lexer-in-python/#comment-1562</link>
		<dc:creator>gooli</dc:creator>
		<pubDate>Wed, 24 Oct 2007 21:14:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.gooli.org/blog/a-simple-lexer-in-python/#comment-1562</guid>
		<description>I don&#039;t think lexing gets that much more complex, at least as long as you aren&#039;t concerned with performance too much. There might be some issues with precedence and you could add support for different start conditions to better support things like C multiline comments. Semantical parsing on the other hand, is a much more complicated matter.

That aperiot module looks really cool. Thanks for the link.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think lexing gets that much more complex, at least as long as you aren&#8217;t concerned with performance too much. There might be some issues with precedence and you could add support for different start conditions to better support things like C multiline comments. Semantical parsing on the other hand, is a much more complicated matter.</p>
<p>That aperiot module looks really cool. Thanks for the link.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kumar McMillan</title>
		<link>http://www.gooli.org/blog/a-simple-lexer-in-python/#comment-1561</link>
		<dc:creator>Kumar McMillan</dc:creator>
		<pubDate>Wed, 24 Oct 2007 21:07:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.gooli.org/blog/a-simple-lexer-in-python/#comment-1561</guid>
		<description>unfortunately, lexical parsing doesn&#039;t remain &quot;simple&quot; for very long!  Last year at Pycon I saw an excellent presentation on aperiot, an easy to use lexical parsing module:
http://moncs.cs.mcgill.ca/people/eposse/projects/aperiot/atglance.dtml
I&#039;ve never had a good reason to try it out though.</description>
		<content:encoded><![CDATA[<p>unfortunately, lexical parsing doesn&#8217;t remain &#8220;simple&#8221; for very long!  Last year at Pycon I saw an excellent presentation on aperiot, an easy to use lexical parsing module:<br />
<a href="http://moncs.cs.mcgill.ca/people/eposse/projects/aperiot/atglance.dtml" rel="nofollow">http://moncs.cs.mcgill.ca/people/eposse/projects/aperiot/atglance.dtml</a><br />
I&#8217;ve never had a good reason to try it out though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gooli</title>
		<link>http://www.gooli.org/blog/a-simple-lexer-in-python/#comment-1549</link>
		<dc:creator>gooli</dc:creator>
		<pubDate>Mon, 22 Oct 2007 07:19:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.gooli.org/blog/a-simple-lexer-in-python/#comment-1549</guid>
		<description>@James
I did look at the tokenize module, but it can only tokenize Python code. That&#039;s great it all you need to do is syntax highlight Python code. But it&#039;s not a generic syntax highlighter. The implementation seems to be similar to what I&#039;ve done although much more complete of course.</description>
		<content:encoded><![CDATA[<p>@James<br />
I did look at the tokenize module, but it can only tokenize Python code. That&#8217;s great it all you need to do is syntax highlight Python code. But it&#8217;s not a generic syntax highlighter. The implementation seems to be similar to what I&#8217;ve done although much more complete of course.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

