<?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: Naïve Text Parsing in Scala</title>
	<atom:link href="http://www.codecommit.com/blog/scala/naive-text-parsing-in-scala/feed" rel="self" type="application/rss+xml" />
	<link>http://www.codecommit.com/blog/scala/naive-text-parsing-in-scala</link>
	<description>(permanently in beta)</description>
	<lastBuildDate>Mon, 09 Jan 2012 20:21:24 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mark</title>
		<link>http://www.codecommit.com/blog/scala/naive-text-parsing-in-scala/comment-page-1#comment-3684</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Sun, 01 Jun 2008 23:51:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.codecommit.com/blog/scala/naive-text-parsing-in-scala#comment-3684</guid>
		<description>Nice post, I&#039;m thinking there is a smaller, more svelte implementation hiding in there somewhere... :P</description>
		<content:encoded><![CDATA[<p>Nice post, I&#8217;m thinking there is a smaller, more svelte implementation hiding in there somewhere&#8230; <img src='http://www.codecommit.com/blog/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Linsin</title>
		<link>http://www.codecommit.com/blog/scala/naive-text-parsing-in-scala/comment-page-1#comment-3682</link>
		<dc:creator>David Linsin</dc:creator>
		<pubDate>Sun, 01 Jun 2008 10:39:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.codecommit.com/blog/scala/naive-text-parsing-in-scala#comment-3682</guid>
		<description>Awesome blog post! Keep it coming, it&#039;s always fun to follow you on these little journeys!</description>
		<content:encoded><![CDATA[<p>Awesome blog post! Keep it coming, it&#8217;s always fun to follow you on these little journeys!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Spiewak</title>
		<link>http://www.codecommit.com/blog/scala/naive-text-parsing-in-scala/comment-page-1#comment-3663</link>
		<dc:creator>Daniel Spiewak</dc:creator>
		<pubDate>Mon, 26 May 2008 16:29:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.codecommit.com/blog/scala/naive-text-parsing-in-scala#comment-3663</guid>
		<description>I considered using parser combinators, however they would be overkill for a number of reasons.  The entire syntax for C-style printf can be written as a regular expression, thus there is no need for a full pushdown automaton (as mentioned in the post).  DFAs are far more efficient than PDAs (because there is no need for a supplementary stack) and also tend to be easier to work with when written by hand.  It&#039;s actually *harder* to properly express printf as a CFG than it is to just bull ahead with a DFA (I had to formulate the printf grammar specifically for this post, I didn&#039;t use it at all in my implementation).

It is true that parser combinators would probably be easier to read than my hand-coded approach, but I think the reduced efficiency would be too much of a tradeoff.  I haven&#039;t spent much time optimizing my parser (read: none at all), but according to my test results, it&#039;s almost as fast as the well-vetted JDK implementation.  If that&#039;s the case, then theoretically I can squeeze at least as much performance out of it, maybe even better.  I don&#039;t really have this opportunity if I use a pre-baked parser generator.</description>
		<content:encoded><![CDATA[<p>I considered using parser combinators, however they would be overkill for a number of reasons.  The entire syntax for C-style printf can be written as a regular expression, thus there is no need for a full pushdown automaton (as mentioned in the post).  DFAs are far more efficient than PDAs (because there is no need for a supplementary stack) and also tend to be easier to work with when written by hand.  It&#8217;s actually *harder* to properly express printf as a CFG than it is to just bull ahead with a DFA (I had to formulate the printf grammar specifically for this post, I didn&#8217;t use it at all in my implementation).</p>
<p>It is true that parser combinators would probably be easier to read than my hand-coded approach, but I think the reduced efficiency would be too much of a tradeoff.  I haven&#8217;t spent much time optimizing my parser (read: none at all), but according to my test results, it&#8217;s almost as fast as the well-vetted JDK implementation.  If that&#8217;s the case, then theoretically I can squeeze at least as much performance out of it, maybe even better.  I don&#8217;t really have this opportunity if I use a pre-baked parser generator.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Camerer</title>
		<link>http://www.codecommit.com/blog/scala/naive-text-parsing-in-scala/comment-page-1#comment-3662</link>
		<dc:creator>Justin Camerer</dc:creator>
		<pubDate>Mon, 26 May 2008 16:15:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.codecommit.com/blog/scala/naive-text-parsing-in-scala#comment-3662</guid>
		<description>Great post! I really enjoy every post you do on Scala. I am learning Scala and (re)learning many FP ideas, and your blog has been a great help.

I don&#039;t think I&#039;d be of much help, but I&#039;d still love to see the code and specs if you had time to ship them my way.

Thanks,
Justin</description>
		<content:encoded><![CDATA[<p>Great post! I really enjoy every post you do on Scala. I am learning Scala and (re)learning many FP ideas, and your blog has been a great help.</p>
<p>I don&#8217;t think I&#8217;d be of much help, but I&#8217;d still love to see the code and specs if you had time to ship them my way.</p>
<p>Thanks,<br />
Justin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Torreborre</title>
		<link>http://www.codecommit.com/blog/scala/naive-text-parsing-in-scala/comment-page-1#comment-3657</link>
		<dc:creator>Eric Torreborre</dc:creator>
		<pubDate>Mon, 26 May 2008 08:51:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.codecommit.com/blog/scala/naive-text-parsing-in-scala#comment-3657</guid>
		<description>Hi Daniel,

I am a real fan of your blog, you write very frequent and interesting posts

Could you send me your spec please? I&#039;m interested to see how you and other users are using the library, to refine and improve it.

Back to the subject, wouldn&#039;t it be a good idea anyway to use parser combinators, in terms of:

-readability of what the implementation does?
-speed of implementation?

Thanks,

Eric.</description>
		<content:encoded><![CDATA[<p>Hi Daniel,</p>
<p>I am a real fan of your blog, you write very frequent and interesting posts</p>
<p>Could you send me your spec please? I&#8217;m interested to see how you and other users are using the library, to refine and improve it.</p>
<p>Back to the subject, wouldn&#8217;t it be a good idea anyway to use parser combinators, in terms of:</p>
<p>-readability of what the implementation does?<br />
-speed of implementation?</p>
<p>Thanks,</p>
<p>Eric.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

