<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Time window matcher</title>
	<link>http://www.lispcast.com/wordpress/2007/10/time-window-matcher/</link>
	<description></description>
	<pubDate>Tue, 18 Nov 2008 15:21:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: LOOP Macro Love &#124; LispCast</title>
		<link>http://www.lispcast.com/wordpress/2007/10/time-window-matcher/#comment-462</link>
		<dc:creator>LOOP Macro Love &#124; LispCast</dc:creator>
		<pubDate>Mon, 05 Nov 2007 05:26:03 +0000</pubDate>
		<guid>http://www.lispcast.com/wordpress/2007/10/time-window-matcher/#comment-462</guid>
		<description>[...] I&#8217;ve re-written my time-window code. It&#8217;s cleaner, it compiles the matchers to nested lambdas (so it&#8217;s faster), and now it [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] I&#8217;ve re-written my time-window code. It&#8217;s cleaner, it compiles the matchers to nested lambdas (so it&#8217;s faster), and now it [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anton</title>
		<link>http://www.lispcast.com/wordpress/2007/10/time-window-matcher/#comment-461</link>
		<dc:creator>Anton</dc:creator>
		<pubDate>Sun, 04 Nov 2007 14:23:00 +0000</pubDate>
		<guid>http://www.lispcast.com/wordpress/2007/10/time-window-matcher/#comment-461</guid>
		<description>&#62; So, right now, I’m looking for a challenge to post to
&#62; the comp.lang.ruby newsgroup. I want one that will
&#62; rattle them to the bone about the inadequacy of
&#62; their language. Nothing big, just a whopper to get
&#62; them thinking. Do you have any ideas? Let’s give
&#62; them something to talk about.

As a last resort we may just write to comp.lang.ruby that they are idiots.</description>
		<content:encoded><![CDATA[<p>&gt; So, right now, I’m looking for a challenge to post to<br />
&gt; the comp.lang.ruby newsgroup. I want one that will<br />
&gt; rattle them to the bone about the inadequacy of<br />
&gt; their language. Nothing big, just a whopper to get<br />
&gt; them thinking. Do you have any ideas? Let’s give<br />
&gt; them something to talk about.</p>
<p>As a last resort we may just write to comp.lang.ruby that they are idiots.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.lispcast.com/wordpress/2007/10/time-window-matcher/#comment-460</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Fri, 26 Oct 2007 18:02:27 +0000</pubDate>
		<guid>http://www.lispcast.com/wordpress/2007/10/time-window-matcher/#comment-460</guid>
		<description>You're right, they're the same.  This tells me I need to read the docs a little better.

Thanks!</description>
		<content:encoded><![CDATA[<p>You&#8217;re right, they&#8217;re the same.  This tells me I need to read the docs a little better.</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zach Beane</title>
		<link>http://www.lispcast.com/wordpress/2007/10/time-window-matcher/#comment-459</link>
		<dc:creator>Zach Beane</dc:creator>
		<pubDate>Fri, 26 Oct 2007 11:10:00 +0000</pubDate>
		<guid>http://www.lispcast.com/wordpress/2007/10/time-window-matcher/#comment-459</guid>
		<description>Are you aware of CL-PPCRE:REGISTER-GROUPS-BIND? How does it differ from your SCAN-AND-BIND?</description>
		<content:encoded><![CDATA[<p>Are you aware of CL-PPCRE:REGISTER-GROUPS-BIND? How does it differ from your SCAN-AND-BIND?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.lispcast.com/wordpress/2007/10/time-window-matcher/#comment-458</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Thu, 25 Oct 2007 23:24:34 +0000</pubDate>
		<guid>http://www.lispcast.com/wordpress/2007/10/time-window-matcher/#comment-458</guid>
		<description>Well, now that I think about it, I could do a better parser with a regular-expression-cond form. . .
What an idea!</description>
		<content:encoded><![CDATA[<p>Well, now that I think about it, I could do a better parser with a regular-expression-cond form. . .<br />
What an idea!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
