<?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 on: Selectors as Blocks</title>
	<atom:link href="http://blog.3plus4.org/2007/03/27/selectors-as-blocks/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.3plus4.org/2007/03/27/selectors-as-blocks/</link>
	<description>The neighbourhood of 7</description>
	<pubDate>Wed, 20 Aug 2008 02:55:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Travis Griggs</title>
		<link>http://blog.3plus4.org/2007/03/27/selectors-as-blocks/#comment-16</link>
		<dc:creator>Travis Griggs</dc:creator>
		<pubDate>Wed, 28 Mar 2007 17:57:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.3plus4.org/2007/03/27/selectors-as-blocks/#comment-16</guid>
		<description>That's cool Vassili. I still like the simplicity of Symbol&#62;&#62;value of course. But I like the asBlock pattern for the bigger items. Thogh I use them less.

You rightly point out that it gets us around the code that "checks" for numArgs. To me, this is where the real fault lies at though. The numArgs API is ambiguous based on the intended use as an either a selector or an evaluator.</description>
		<content:encoded><![CDATA[<p>That&#8217;s cool Vassili. I still like the simplicity of Symbol&gt;&gt;value of course. But I like the asBlock pattern for the bigger items. Thogh I use them less.</p>
<p>You rightly point out that it gets us around the code that &#8220;checks&#8221; for numArgs. To me, this is where the real fault lies at though. The numArgs API is ambiguous based on the intended use as an either a selector or an evaluator.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vassili Bykov</title>
		<link>http://blog.3plus4.org/2007/03/27/selectors-as-blocks/#comment-15</link>
		<dc:creator>Vassili Bykov</dc:creator>
		<pubDate>Wed, 28 Mar 2007 16:52:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.3plus4.org/2007/03/27/selectors-as-blocks/#comment-15</guid>
		<description>Sure, but that doesn't solve the problem of numArgs breaking the illusion.</description>
		<content:encoded><![CDATA[<p>Sure, but that doesn&#8217;t solve the problem of numArgs breaking the illusion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan Knight</title>
		<link>http://blog.3plus4.org/2007/03/27/selectors-as-blocks/#comment-14</link>
		<dc:creator>Alan Knight</dc:creator>
		<pubDate>Wed, 28 Mar 2007 16:20:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.3plus4.org/2007/03/27/selectors-as-blocks/#comment-14</guid>
		<description>I don't understand why this is better than Symbol&#62;&#62;value: for multiple-argument selectors. It seems to me that you can do exactly the same thing by implementing Symbol&#62;&#62;value:value:</description>
		<content:encoded><![CDATA[<p>I don&#8217;t understand why this is better than Symbol&gt;&gt;value: for multiple-argument selectors. It seems to me that you can do exactly the same thing by implementing Symbol&gt;&gt;value:value:</p>
]]></content:encoded>
	</item>
</channel>
</rss>
