<?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"
	>
<channel>
	<title>Comments for Paul Findlay</title>
	<atom:link href="http://findlay.net.nz/paul/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://findlay.net.nz/paul</link>
	<description>Paul Findlay and his online content</description>
	<pubDate>Wed, 07 Jan 2009 05:01:12 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>Comment on XML: Parser by Cowtowncoder</title>
		<link>http://findlay.net.nz/paul/2007/07/04/xml-parser#comment-35</link>
		<dc:creator>Cowtowncoder</dc:creator>
		<pubDate>Fri, 12 Oct 2007 23:41:16 +0000</pubDate>
		<guid isPermaLink="false">http://findlay.net.nz/paul/2007/07/04/xml-parser#comment-35</guid>
		<description>Hey Paul, good luck with the development! Like I said, it's a non-trivial task. But I think using a state machine is a good idea (in case it wasn't obvious from my first comment), and it was something I was thinking about too. In the end choice had more to do with possibility to recycle some existing pieces, than feasibility of approaches.
I hope to learn more about the implementation if and when you get that far.</description>
		<content:encoded><![CDATA[<p>Hey Paul, good luck with the development! Like I said, it&#8217;s a non-trivial task. But I think using a state machine is a good idea (in case it wasn&#8217;t obvious from my first comment), and it was something I was thinking about too. In the end choice had more to do with possibility to recycle some existing pieces, than feasibility of approaches.<br />
I hope to learn more about the implementation if and when you get that far.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Fingers crossed by Dave</title>
		<link>http://findlay.net.nz/paul/2007/10/03/fingers-crossed#comment-34</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Wed, 03 Oct 2007 21:10:01 +0000</pubDate>
		<guid isPermaLink="false">http://findlay.net.nz/paul/2007/10/03/fingers-crossed#comment-34</guid>
		<description>While you are finding something to do, you could work through all those books you have been amassing.</description>
		<content:encoded><![CDATA[<p>While you are finding something to do, you could work through all those books you have been amassing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on XML: Parser by Paul Findlay &#187; XML: Impossible to be original</title>
		<link>http://findlay.net.nz/paul/2007/07/04/xml-parser#comment-33</link>
		<dc:creator>Paul Findlay &#187; XML: Impossible to be original</dc:creator>
		<pubDate>Thu, 19 Jul 2007 22:46:59 +0000</pubDate>
		<guid isPermaLink="false">http://findlay.net.nz/paul/2007/07/04/xml-parser#comment-33</guid>
		<description>[...] combination of these XPath expressions get applied like a giant state-machine/trie to the incoming XML events in something approximating log(n) time, so large numbers of XML streams can be handled [...]</description>
		<content:encoded><![CDATA[<p>[...] combination of these XPath expressions get applied like a giant state-machine/trie to the incoming XML events in something approximating log(n) time, so large numbers of XML streams can be handled [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on XML: Parser by Paul</title>
		<link>http://findlay.net.nz/paul/2007/07/04/xml-parser#comment-32</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Thu, 19 Jul 2007 14:05:40 +0000</pubDate>
		<guid isPermaLink="false">http://findlay.net.nz/paul/2007/07/04/xml-parser#comment-32</guid>
		<description>I'm glad you have done it, and thanks for the encouragement :) Woodstox is the parser mine looks up to..

I hope the FSM thing works out for me, since its somewhere around 400 states already (I could reduce that by making it a pushdown automata..), utf characters get decoded to Unicode only as they are needed. I plan on using what I call a "Tim Bray technique" where chars &gt; 128 get transformed to corresponding ASCII characters for the sake of keeping the transition characters in the FSM low, but inside the state the original Unicode character is checked for its validity to be present in whatever part of the document we are looking at. Perhaps if profiling shows to much work is being done, I could make it happen over longer runs of characters.

Yes, I want it to be a niche thing (and it should be just because it is written for the &lt;a href="http://www.digitalmars.com/d/" rel="nofollow"&gt;D programming language&lt;/a&gt;), and you did read my intentions right. I want the parser to be suitable for environments like jabber servers or handling thousands of concurrent REST requests etc. I'm not sure anyone cares to do this at such a low level, so I may end up building some recursive descent parser generator that fits with an asynchronous IO framework..

Hopefully someone wants to pay me somehow for the end usage to compensate for being the only person in the world who cares :)</description>
		<content:encoded><![CDATA[<p>I&#8217;m glad you have done it, and thanks for the encouragement <img src='http://findlay.net.nz/paul/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> Woodstox is the parser mine looks up to..</p>
<p>I hope the FSM thing works out for me, since its somewhere around 400 states already (I could reduce that by making it a pushdown automata..), utf characters get decoded to Unicode only as they are needed. I plan on using what I call a &#8220;Tim Bray technique&#8221; where chars > 128 get transformed to corresponding ASCII characters for the sake of keeping the transition characters in the FSM low, but inside the state the original Unicode character is checked for its validity to be present in whatever part of the document we are looking at. Perhaps if profiling shows to much work is being done, I could make it happen over longer runs of characters.</p>
<p>Yes, I want it to be a niche thing (and it should be just because it is written for the <a href="http://www.digitalmars.com/d/" rel="nofollow">D programming language</a>), and you did read my intentions right. I want the parser to be suitable for environments like jabber servers or handling thousands of concurrent REST requests etc. I&#8217;m not sure anyone cares to do this at such a low level, so I may end up building some recursive descent parser generator that fits with an asynchronous IO framework..</p>
<p>Hopefully someone wants to pay me somehow for the end usage to compensate for being the only person in the world who cares <img src='http://findlay.net.nz/paul/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on XML: Parser by Cowtowncoder</title>
		<link>http://findlay.net.nz/paul/2007/07/04/xml-parser#comment-31</link>
		<dc:creator>Cowtowncoder</dc:creator>
		<pubDate>Wed, 18 Jul 2007 20:29:50 +0000</pubDate>
		<guid isPermaLink="false">http://findlay.net.nz/paul/2007/07/04/xml-parser#comment-31</guid>
		<description>Yes. But definitely doable.
Now, assuming I understand you right, one main benefit would be the ability to do non-blocking parsing: that is, either get next event, or indication of "not enough data yet to know". For what it's worth, I actually have written core of such a parser, and one that does implement Stax API too. At this point the main challenge is figuring out who would care enough to want to get it ready for real use. ;-)

There are already enough good-but-blocking parsers for this to be bit of a niche thing I suppose.
Oh, also, I didn't use FSM, but that's mostly since it gets rather hairy when one wants to also integrate utf-decoding with parsing, for further performance gains.</description>
		<content:encoded><![CDATA[<p>Yes. But definitely doable.<br />
Now, assuming I understand you right, one main benefit would be the ability to do non-blocking parsing: that is, either get next event, or indication of &#8220;not enough data yet to know&#8221;. For what it&#8217;s worth, I actually have written core of such a parser, and one that does implement Stax API too. At this point the main challenge is figuring out who would care enough to want to get it ready for real use. <img src='http://findlay.net.nz/paul/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>There are already enough good-but-blocking parsers for this to be bit of a niche thing I suppose.<br />
Oh, also, I didn&#8217;t use FSM, but that&#8217;s mostly since it gets rather hairy when one wants to also integrate utf-decoding with parsing, for further performance gains.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Hilarious by Paul</title>
		<link>http://findlay.net.nz/paul/2006/06/08/hilarious#comment-16</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Wed, 12 Jul 2006 14:15:31 +0000</pubDate>
		<guid isPermaLink="false">http://findlay.net.nz/paul/2006/06/08/hilarious#comment-16</guid>
		<description>Pre Increment/Decrement (++i/--i) commit the action, then return its new value, whereas Post Increment/Decrement (i++/i--) return the current value, then commit the change.</description>
		<content:encoded><![CDATA[<p>Pre Increment/Decrement (+<ins>i/-<del>i) commit the action, then return its new value, whereas Post Increment/Decrement (i</del></ins>+/i-) return the current value, then commit the change.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on XML Apis by Dave</title>
		<link>http://findlay.net.nz/paul/2006/06/15/xml-apis#comment-8</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Thu, 15 Jun 2006 23:36:19 +0000</pubDate>
		<guid isPermaLink="false">http://findlay.net.nz/paul/2006/06/15/xml-apis#comment-8</guid>
		<description>Paul, this is...an interesting post.</description>
		<content:encoded><![CDATA[<p>Paul, this is&#8230;an interesting post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Excerpt from The Brothers Karamazov by Dave</title>
		<link>http://findlay.net.nz/paul/2006/03/14/excerpt-from-the-brothers-karamazov#comment-6</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Wed, 03 May 2006 03:41:59 +0000</pubDate>
		<guid isPermaLink="false">http://findlay.net.nz/paul/?p=16#comment-6</guid>
		<description>I waded through Brothers a few summers ago and, although the going was tough, I'm glad I did it. Some of the large dialogues between the Ivan (I think) and Alexey made for compelling reading.

Hey - have you read "The Da Vinci Code" yet? I thought I might do so whan I get my hands on a copy.</description>
		<content:encoded><![CDATA[<p>I waded through Brothers a few summers ago and, although the going was tough, I&#8217;m glad I did it. Some of the large dialogues between the Ivan (I think) and Alexey made for compelling reading.</p>
<p>Hey &#8211; have you read &#8220;The Da Vinci Code&#8221; yet? I thought I might do so whan I get my hands on a copy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Protected: Confessional by Marcus</title>
		<link>http://findlay.net.nz/paul/2005/11/26/confessional#comment-5</link>
		<dc:creator>Marcus</dc:creator>
		<pubDate>Sat, 26 Nov 2005 02:51:13 +0000</pubDate>
		<guid isPermaLink="false">http://findlay.net.nz/paul/?p=13#comment-5</guid>
		<description>Protected Comments: Please enter your password to view comments.</description>
		<content:encoded><![CDATA[<form action="http://findlay.net.nz/paul/wp-pass.php" method="post">
	<p>This post is password protected. To view it please enter your password below:</p>
	<p><label for="pwbox-37">Password: <input name="post_password" id="pwbox-37" type="password" size="20" /></label> <input type="submit" name="Submit" value="Submit" /></p>
	</form>
	]]></content:encoded>
	</item>
	<item>
		<title>Comment on My website is boring by Paul</title>
		<link>http://findlay.net.nz/paul/2005/10/04/my-website-is-boring#comment-4</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Wed, 12 Oct 2005 08:29:21 +0000</pubDate>
		<guid isPermaLink="false">http://findlay.net.nz/paul/?p=7#comment-4</guid>
		<description>I won&#8217;t force alcohol down you, and the drinking is not because of website driven despair.&lt;br /&gt;
&lt;br /&gt;
I tried grey lions but there wasn&#8217;t enough &lt;em&gt;contrast&lt;/em&gt;.</description>
		<content:encoded><![CDATA[<p>I won&#8217;t force alcohol down you, and the drinking is not because of website driven despair.</p>
<p>I tried grey lions but there wasn&#8217;t enough <em>contrast</em>.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
