<?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: Some legal variable names cannot be passed from ActionScript to JavaScript</title>
	<atom:link href="http://joshblog.net/2008/01/03/flash-player-externalinterface-variable-name-bug/feed/" rel="self" type="application/rss+xml" />
	<link>http://joshblog.net/2008/01/03/flash-player-externalinterface-variable-name-bug/</link>
	<description>Josh Tynjala explores Flash, Flex, and ActionScript.</description>
	<lastBuildDate>Sat, 31 Jul 2010 02:55:11 -0400</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Josh Tynjala</title>
		<link>http://joshblog.net/2008/01/03/flash-player-externalinterface-variable-name-bug/comment-page-1/#comment-34328</link>
		<dc:creator>Josh Tynjala</dc:creator>
		<pubDate>Fri, 04 Jan 2008 17:47:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeuslabs.us/2008/01/03/flash-player-externalinterface-variable-name-bug/#comment-34328</guid>
		<description>That&#039;s why you can put quotes around it. Another example would be language keywords (though they pass through ExternalInterface just fine because JavaScript is less strict). &lt;code&gt;myVar.class&lt;/code&gt; leads to a compiler error but &lt;code&gt;myVar[&quot;class&quot;]&lt;/code&gt; doesn&#039;t.

Imagine if you simply couldn&#039;t parse XHTML files with E4X because the &lt;code&gt;class&lt;/code&gt; attribute throws errors. The ability to use string access for variable names is an important &quot;feature of the language&quot;.</description>
		<content:encoded><![CDATA[<p>That&#8217;s why you can put quotes around it. Another example would be language keywords (though they pass through ExternalInterface just fine because JavaScript is less strict). <code>myVar.class</code> leads to a compiler error but <code>myVar["class"]</code> doesn&#8217;t.</p>
<p>Imagine if you simply couldn&#8217;t parse XHTML files with E4X because the <code>class</code> attribute throws errors. The ability to use string access for variable names is an important &#8220;feature of the language&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jon</title>
		<link>http://joshblog.net/2008/01/03/flash-player-externalinterface-variable-name-bug/comment-page-1/#comment-34324</link>
		<dc:creator>jon</dc:creator>
		<pubDate>Fri, 04 Jan 2008 17:03:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeuslabs.us/2008/01/03/flash-player-externalinterface-variable-name-bug/#comment-34324</guid>
		<description>this isnt really a bug IMO
Its a feature of the language in which you cannot use &quot;-&quot; in variable names as the compiler thinks its a minus sign</description>
		<content:encoded><![CDATA[<p>this isnt really a bug IMO<br />
Its a feature of the language in which you cannot use &#8220;-&#8221; in variable names as the compiler thinks its a minus sign</p>
]]></content:encoded>
	</item>
</channel>
</rss>
