<?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: Burned by hoisting</title>
	<atom:link href="http://www.visible-form.com/blog/burned-by-hoisting/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.visible-form.com/blog/burned-by-hoisting/</link>
	<description>Rich Rodecker's blog on flash, flex, actionscript, javascript, and php, with a dash of randomness</description>
	<lastBuildDate>Mon, 28 Jun 2010 12:47:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Bradley</title>
		<link>http://www.visible-form.com/blog/burned-by-hoisting/comment-page-1/#comment-220181</link>
		<dc:creator>Bradley</dc:creator>
		<pubDate>Fri, 30 Oct 2009 18:21:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.visible-form.com/blog/?p=371#comment-220181</guid>
		<description>Eric, the whole point of this post is that AS&#039;s &quot;hosting&quot; feature is useless and the compiler ought to warn about usages that represent programming errors 99.9999% of the time. If that&#039;s not getting &quot;burned&quot;, then what is?

Take your semantic arguments elsewhere, you pusillanimous git.</description>
		<content:encoded><![CDATA[<p>Eric, the whole point of this post is that AS&#8217;s &#8220;hosting&#8221; feature is useless and the compiler ought to warn about usages that represent programming errors 99.9999% of the time. If that&#8217;s not getting &#8220;burned&#8221;, then what is?</p>
<p>Take your semantic arguments elsewhere, you pusillanimous git.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Toland</title>
		<link>http://www.visible-form.com/blog/burned-by-hoisting/comment-page-1/#comment-201388</link>
		<dc:creator>Jon Toland</dc:creator>
		<pubDate>Wed, 08 Apr 2009 18:54:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.visible-form.com/blog/?p=371#comment-201388</guid>
		<description>JavaScript actually has a JSLint tool that warns for this and other ECMAScript oddities.  I&#039;d love to see that integrated with Flex Builder in addition to getting live feedback  while typing about syntactic warnings  and  errors prior to compilation.  As for &quot;hoisting&quot; the next version of ActionScript will provide scoped declaration using the &quot;let&quot; keyword.</description>
		<content:encoded><![CDATA[<p>JavaScript actually has a JSLint tool that warns for this and other ECMAScript oddities.  I&#8217;d love to see that integrated with Flex Builder in addition to getting live feedback  while typing about syntactic warnings  and  errors prior to compilation.  As for &#8220;hoisting&#8221; the next version of ActionScript will provide scoped declaration using the &#8220;let&#8221; keyword.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rich</title>
		<link>http://www.visible-form.com/blog/burned-by-hoisting/comment-page-1/#comment-198476</link>
		<dc:creator>rich</dc:creator>
		<pubDate>Fri, 20 Mar 2009 21:29:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.visible-form.com/blog/?p=371#comment-198476</guid>
		<description>yes, thanks Eric, you&#039;ve summed it up nicely.</description>
		<content:encoded><![CDATA[<p>yes, thanks Eric, you&#8217;ve summed it up nicely.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://www.visible-form.com/blog/burned-by-hoisting/comment-page-1/#comment-198474</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Fri, 20 Mar 2009 21:22:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.visible-form.com/blog/?p=371#comment-198474</guid>
		<description>This is semantics. It appears you are using the word &quot;burned&quot; to imply the compiler was not as helpful as it could be. And true that.

But, if the &lt;code&gt;vo&lt;/code&gt; in line 2 was intended to reference a class member rather than the local variable defined in line 5, the more common application of the word &quot;burned&quot; might apply -- the compiler made changes without warning that caused problems. It doesn&#039;t sound like that was what happened, though (nor should it, because the compiler would track each variable, in it&#039;s appropriate scope, with a unique identifier.

That said, whether the compiler promotes the variables or not, it is good practice to a) declare variables before they are used; b) declare variables just before they are used. 

It would, however, be helpful to folks less-versed in traditional development practices if a compiler flag enabled warnings about conditions like the one you&#039;ve mentioned.

Cheers.</description>
		<content:encoded><![CDATA[<p>This is semantics. It appears you are using the word &#8220;burned&#8221; to imply the compiler was not as helpful as it could be. And true that.</p>
<p>But, if the <code>vo</code> in line 2 was intended to reference a class member rather than the local variable defined in line 5, the more common application of the word &#8220;burned&#8221; might apply &#8212; the compiler made changes without warning that caused problems. It doesn&#8217;t sound like that was what happened, though (nor should it, because the compiler would track each variable, in it&#8217;s appropriate scope, with a unique identifier.</p>
<p>That said, whether the compiler promotes the variables or not, it is good practice to a) declare variables before they are used; b) declare variables just before they are used. </p>
<p>It would, however, be helpful to folks less-versed in traditional development practices if a compiler flag enabled warnings about conditions like the one you&#8217;ve mentioned.</p>
<p>Cheers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rich</title>
		<link>http://www.visible-form.com/blog/burned-by-hoisting/comment-page-1/#comment-198379</link>
		<dc:creator>rich</dc:creator>
		<pubDate>Fri, 20 Mar 2009 06:50:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.visible-form.com/blog/?p=371#comment-198379</guid>
		<description>By burned I meant that normally when someone makes a mistake such as that, you&#039;d expect the compiler to catch it...but it didn&#039;t &quot;fix it&quot;, it let the obvious mistake slide by without any warning or error notices.</description>
		<content:encoded><![CDATA[<p>By burned I meant that normally when someone makes a mistake such as that, you&#8217;d expect the compiler to catch it&#8230;but it didn&#8217;t &#8220;fix it&#8221;, it let the obvious mistake slide by without any warning or error notices.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: w3master</title>
		<link>http://www.visible-form.com/blog/burned-by-hoisting/comment-page-1/#comment-198336</link>
		<dc:creator>w3master</dc:creator>
		<pubDate>Thu, 19 Mar 2009 22:59:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.visible-form.com/blog/?p=371#comment-198336</guid>
		<description>In what way were you &quot;burned&quot;?

You wrote some duff code, used a variable before you declared it, and the compiler fixed it for you?</description>
		<content:encoded><![CDATA[<p>In what way were you &#8220;burned&#8221;?</p>
<p>You wrote some duff code, used a variable before you declared it, and the compiler fixed it for you?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
