<?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: Upon Reflection</title>
	<atom:link href="http://nodename.com/blog/2008/06/15/upon-reflection/feed/" rel="self" type="application/rss+xml" />
	<link>http://nodename.com/blog/2008/06/15/upon-reflection/</link>
	<description></description>
	<pubDate>Fri, 21 Nov 2008 01:21:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: alan</title>
		<link>http://nodename.com/blog/2008/06/15/upon-reflection/#comment-138367</link>
		<dc:creator>alan</dc:creator>
		<pubDate>Tue, 17 Jun 2008 00:31:43 +0000</pubDate>
		<guid isPermaLink="false">http://nodename.com/blog/?p=59#comment-138367</guid>
		<description>Erik -
About the Dictionaries I could say instances -- of Object!  About the Object I could say instances of String.  About the Array, I could say instances of Number.  I don't think that would add anything :)</description>
		<content:encoded><![CDATA[<p>Erik -<br />
About the Dictionaries I could say instances &#8212; of Object!  About the Object I could say instances of String.  About the Array, I could say instances of Number.  I don&#8217;t think that would add anything :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik</title>
		<link>http://nodename.com/blog/2008/06/15/upon-reflection/#comment-138278</link>
		<dc:creator>Erik</dc:creator>
		<pubDate>Mon, 16 Jun 2008 09:50:05 +0000</pubDate>
		<guid isPermaLink="false">http://nodename.com/blog/?p=59#comment-138278</guid>
		<description>About the Dictionaries, instead of Objects (which could be confusing) you could say instances. Dictionary is not using the toString method to determine the uniqueness of the key.

About the prototype.isPrototypeOf method: too bad it doesn't work for interfaces...


Greetz Erik</description>
		<content:encoded><![CDATA[<p>About the Dictionaries, instead of Objects (which could be confusing) you could say instances. Dictionary is not using the toString method to determine the uniqueness of the key.</p>
<p>About the prototype.isPrototypeOf method: too bad it doesn&#8217;t work for interfaces&#8230;</p>
<p>Greetz Erik</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Series of ways to use Classes from assorted objects : Mark Badger:Comics &#38; Code</title>
		<link>http://nodename.com/blog/2008/06/15/upon-reflection/#comment-138249</link>
		<dc:creator>Series of ways to use Classes from assorted objects : Mark Badger:Comics &#38; Code</dc:creator>
		<pubDate>Mon, 16 Jun 2008 04:53:57 +0000</pubDate>
		<guid isPermaLink="false">http://nodename.com/blog/?p=59#comment-138249</guid>
		<description>[...] is here [...]</description>
		<content:encoded><![CDATA[<p>[...] is here [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alan</title>
		<link>http://nodename.com/blog/2008/06/15/upon-reflection/#comment-138245</link>
		<dc:creator>alan</dc:creator>
		<pubDate>Mon, 16 Jun 2008 04:36:36 +0000</pubDate>
		<guid isPermaLink="false">http://nodename.com/blog/?p=59#comment-138245</guid>
		<description>I don't know about Dictionaries in Java, but in AS3, this is precisely what distinguishes a Dictionary from an Object.  To quote the Flex 3 Language Reference:

The Dictionary class lets you create a dynamic collection of properties, which uses strict equality (===) for key comparison on non-primitive object keys. When an object is used as a key, the object's identity is used to look up the object, and not the value returned from calling toString() on it. Primitive (built-in) objects, like Numbers, in a Dictionary collection behave in the same manner as they do when they are the property of a regular object.
</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know about Dictionaries in Java, but in AS3, this is precisely what distinguishes a Dictionary from an Object.  To quote the Flex 3 Language Reference:</p>
<p>The Dictionary class lets you create a dynamic collection of properties, which uses strict equality (===) for key comparison on non-primitive object keys. When an object is used as a key, the object&#8217;s identity is used to look up the object, and not the value returned from calling toString() on it. Primitive (built-in) objects, like Numbers, in a Dictionary collection behave in the same manner as they do when they are the property of a regular object.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danny Miller</title>
		<link>http://nodename.com/blog/2008/06/15/upon-reflection/#comment-138242</link>
		<dc:creator>Danny Miller</dc:creator>
		<pubDate>Mon, 16 Jun 2008 04:17:22 +0000</pubDate>
		<guid isPermaLink="false">http://nodename.com/blog/?p=59#comment-138242</guid>
		<description>I think
"Dictionary: properties indexed by Objects"
might be a bit misleading. I could be wrong, but I always thought that Dictionary has properties indexed by the toString value of objects. If you have two objects with the same toString, will they be different in the Dictionary object? That's how I always envisioned it; I think Java is similar in that regard.</description>
		<content:encoded><![CDATA[<p>I think<br />
&#8220;Dictionary: properties indexed by Objects&#8221;<br />
might be a bit misleading. I could be wrong, but I always thought that Dictionary has properties indexed by the toString value of objects. If you have two objects with the same toString, will they be different in the Dictionary object? That&#8217;s how I always envisioned it; I think Java is similar in that regard.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
