<?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: An Objective Look at Javascript 2.0: Strong Typing</title>
	<atom:link href="http://timkadlec.com/2008/04/an-objective-look-at-javascript-2-0-strong-typing/feed/" rel="self" type="application/rss+xml" />
	<link>http://timkadlec.com/2008/04/an-objective-look-at-javascript-2-0-strong-typing/</link>
	<description>A Wisconsin based web developer writing about the web.</description>
	<lastBuildDate>Tue, 13 Jul 2010 17:23:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: James Justin Harrell</title>
		<link>http://timkadlec.com/2008/04/an-objective-look-at-javascript-2-0-strong-typing/comment-page-1/#comment-72</link>
		<dc:creator>James Justin Harrell</dc:creator>
		<pubDate>Wed, 30 Apr 2008 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/1969/12/an-objective-look-at-javascript-2-0-strong-typing/#comment-72</guid>
		<description>Terms like &#039;strong typing&#039; and &#039;loose typing&#039; are so vague as to be meaningless. If you&#039;re going to use them, you should first define them.</description>
		<content:encoded><![CDATA[<p>Terms like &#8216;strong typing&#8217; and &#8216;loose typing&#8217; are so vague as to be meaningless. If you&#8217;re going to use them, you should first define them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Kadlec</title>
		<link>http://timkadlec.com/2008/04/an-objective-look-at-javascript-2-0-strong-typing/comment-page-1/#comment-73</link>
		<dc:creator>Tim Kadlec</dc:creator>
		<pubDate>Wed, 30 Apr 2008 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/1969/12/an-objective-look-at-javascript-2-0-strong-typing/#comment-73</guid>
		<description>@James - Apologies for the confusion. In the terms of the article - a loosely typed system doesn&#039;t enforce type annotations. In a loosely typed system, blocks of data appearing to be of one type can be treated as another. In a strongly typed system, those blocks of data must first be explicitly converted to the desired type.</description>
		<content:encoded><![CDATA[<p>@James &#8211; Apologies for the confusion. In the terms of the article &#8211; a loosely typed system doesn&#8217;t enforce type annotations. In a loosely typed system, blocks of data appearing to be of one type can be treated as another. In a strongly typed system, those blocks of data must first be explicitly converted to the desired type.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrien F.</title>
		<link>http://timkadlec.com/2008/04/an-objective-look-at-javascript-2-0-strong-typing/comment-page-1/#comment-74</link>
		<dc:creator>Adrien F.</dc:creator>
		<pubDate>Wed, 30 Apr 2008 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/1969/12/an-objective-look-at-javascript-2-0-strong-typing/#comment-74</guid>
		<description>&#039;In the terms of the article - a loosely typed system doesn&#039;t enforce type annotations.&#039;&lt;br /&gt;&lt;br /&gt;I disagree with this part of you comment. For example, OCaml is a very strongly typed language, and type annotations are optional (and almoste never used). On the other hand, C has a loosely typed system, but annotations are enforced...</description>
		<content:encoded><![CDATA[<p>&#8216;In the terms of the article &#8211; a loosely typed system doesn&#8217;t enforce type annotations.&#8217;</p>
<p>I disagree with this part of you comment. For example, OCaml is a very strongly typed language, and type annotations are optional (and almoste never used). On the other hand, C has a loosely typed system, but annotations are enforced&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike McNally</title>
		<link>http://timkadlec.com/2008/04/an-objective-look-at-javascript-2-0-strong-typing/comment-page-1/#comment-70</link>
		<dc:creator>Mike McNally</dc:creator>
		<pubDate>Tue, 29 Apr 2008 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/1969/12/an-objective-look-at-javascript-2-0-strong-typing/#comment-70</guid>
		<description>That function declaration (line 4 of the first set of examples) seems wrong. What are the formal parameter names?</description>
		<content:encoded><![CDATA[<p>That function declaration (line 4 of the first set of examples) seems wrong. What are the formal parameter names?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Kadlec</title>
		<link>http://timkadlec.com/2008/04/an-objective-look-at-javascript-2-0-strong-typing/comment-page-1/#comment-71</link>
		<dc:creator>Tim Kadlec</dc:creator>
		<pubDate>Tue, 29 Apr 2008 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/1969/12/an-objective-look-at-javascript-2-0-strong-typing/#comment-71</guid>
		<description>@Mike - You are absolutely correct....there should be formal parameter names. Apparently I didn&#039;t proof-read as well as I had thought! I went back and added some formal parameter names in now so the syntax is correct. Sorry for the confusion.</description>
		<content:encoded><![CDATA[<p>@Mike &#8211; You are absolutely correct&#8230;.there should be formal parameter names. Apparently I didn&#8217;t proof-read as well as I had thought! I went back and added some formal parameter names in now so the syntax is correct. Sorry for the confusion.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
