<?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: AS3 compiler open-source: the logical consequences</title>
	<atom:link href="http://blog.joa-ebert.com/2008/02/28/flex-compiler-open-source-the-logical-consequences/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.joa-ebert.com/2008/02/28/flex-compiler-open-source-the-logical-consequences/</link>
	<description>Actionscript3, Flash, Scala, Java, C#, C++, Algorithms &#38; Imageprocessing</description>
	<lastBuildDate>Sun, 05 Feb 2012 21:26:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: RUAmentalist (Richard Johnson)</title>
		<link>http://blog.joa-ebert.com/2008/02/28/flex-compiler-open-source-the-logical-consequences/comment-page-1/#comment-229095</link>
		<dc:creator>RUAmentalist (Richard Johnson)</dc:creator>
		<pubDate>Mon, 21 Feb 2011 19:02:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.je2050.de/2008/02/28/flex-compiler-open-source-the-logical-consequences/#comment-229095</guid>
		<description>&lt;a rel=&quot;nofollow&quot; href=&quot;http://twitter.com/DavidArno&quot;&gt;@DavidArno&lt;/a&gt; ask Joe http://blog.joa-ebert.com/2008/02/28/flex-compiler-open-source-the-logical-consequences/</description>
		<content:encoded><![CDATA[<p><a rel="nofollow" href="http://twitter.com/DavidArno">@DavidArno</a> ask Joe <a href="http://blog.joa-ebert.com/2008/02/28/flex-compiler-open-source-the-logical-consequences/" rel="nofollow">http://blog.joa-ebert.com/2008/02/28/flex-compiler-open-source-the-logical-consequences/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The logical consequences that never happened at controul</title>
		<link>http://blog.joa-ebert.com/2008/02/28/flex-compiler-open-source-the-logical-consequences/comment-page-1/#comment-166142</link>
		<dc:creator>The logical consequences that never happened at controul</dc:creator>
		<pubDate>Sun, 22 Mar 2009 17:32:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.je2050.de/2008/02/28/flex-compiler-open-source-the-logical-consequences/#comment-166142</guid>
		<description>[...] than an year ago, Joa Ebert posted a brief summary of the &#8220;logical consequences&#8221; of Adobe&#8217;s opening of the Flex SDK sources. Now that we had the source for a working [...]</description>
		<content:encoded><![CDATA[<p>[...] than an year ago, Joa Ebert posted a brief summary of the &#8220;logical consequences&#8221; of Adobe&#8217;s opening of the Flex SDK sources. Now that we had the source for a working [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adobe Alchemy, is it ActionScript heresy ?</title>
		<link>http://blog.joa-ebert.com/2008/02/28/flex-compiler-open-source-the-logical-consequences/comment-page-1/#comment-163352</link>
		<dc:creator>Adobe Alchemy, is it ActionScript heresy ?</dc:creator>
		<pubDate>Fri, 28 Nov 2008 15:32:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.je2050.de/2008/02/28/flex-compiler-open-source-the-logical-consequences/#comment-163352</guid>
		<description>[...] platform to utilize this &#8220;magically&#8221; acquired speed seems somewhat illogical to me ? Joa Ebert already showed us some work he had done on the compiler, allowing for inline bytecode to be used. Nicolas shows us he [...]</description>
		<content:encoded><![CDATA[<p>[...] platform to utilize this &#8220;magically&#8221; acquired speed seems somewhat illogical to me ? Joa Ebert already showed us some work he had done on the compiler, allowing for inline bytecode to be used. Nicolas shows us he [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joa</title>
		<link>http://blog.joa-ebert.com/2008/02/28/flex-compiler-open-source-the-logical-consequences/comment-page-1/#comment-62517</link>
		<dc:creator>joa</dc:creator>
		<pubDate>Wed, 12 Mar 2008 13:33:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.je2050.de/2008/02/28/flex-compiler-open-source-the-logical-consequences/#comment-62517</guid>
		<description>Metal: I know about hxasm for a long time and on the old AS3C roadmap is still the port to haXe.

I am in contact with Nicolas for certain issues and he helped me a lot during the past. The only problem is right now that I do not find the time to port all the code to haXe because I want to do it right and therefore I have to write a lot of stuff (starting with a haXe ByteArray for instance).

I also though about integrating what my tool does into the real ASC but for several reasons I think it would be a bad idea.</description>
		<content:encoded><![CDATA[<p>Metal: I know about hxasm for a long time and on the old AS3C roadmap is still the port to haXe.</p>
<p>I am in contact with Nicolas for certain issues and he helped me a lot during the past. The only problem is right now that I do not find the time to port all the code to haXe because I want to do it right and therefore I have to write a lot of stuff (starting with a haXe ByteArray for instance).</p>
<p>I also though about integrating what my tool does into the real ASC but for several reasons I think it would be a bad idea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Metal</title>
		<link>http://blog.joa-ebert.com/2008/02/28/flex-compiler-open-source-the-logical-consequences/comment-page-1/#comment-62435</link>
		<dc:creator>Metal</dc:creator>
		<pubDate>Wed, 12 Mar 2008 05:56:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.je2050.de/2008/02/28/flex-compiler-open-source-the-logical-consequences/#comment-62435</guid>
		<description>Yup. eval() is probably the most misused construct in javascript.

I think a closer match for your project might be Haxe&#039;s hxasm project: http://haxe.org/hxasm

It&#039;s probably more fun to write your own, but you might be able to compare notes, or something.

On the other hand, tamarin does include a bytecode emitter, which would allow one to pick which bytecodes to put together at runtime..</description>
		<content:encoded><![CDATA[<p>Yup. eval() is probably the most misused construct in javascript.</p>
<p>I think a closer match for your project might be Haxe&#8217;s hxasm project: <a href="http://haxe.org/hxasm" rel="nofollow">http://haxe.org/hxasm</a></p>
<p>It&#8217;s probably more fun to write your own, but you might be able to compare notes, or something.</p>
<p>On the other hand, tamarin does include a bytecode emitter, which would allow one to pick which bytecodes to put together at runtime..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rackdoll</title>
		<link>http://blog.joa-ebert.com/2008/02/28/flex-compiler-open-source-the-logical-consequences/comment-page-1/#comment-56446</link>
		<dc:creator>Rackdoll</dc:creator>
		<pubDate>Fri, 29 Feb 2008 09:17:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.je2050.de/2008/02/28/flex-compiler-open-source-the-logical-consequences/#comment-56446</guid>
		<description>I really like your work joa!
Keep up the good work!</description>
		<content:encoded><![CDATA[<p>I really like your work joa!<br />
Keep up the good work!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joa</title>
		<link>http://blog.joa-ebert.com/2008/02/28/flex-compiler-open-source-the-logical-consequences/comment-page-1/#comment-56436</link>
		<dc:creator>joa</dc:creator>
		<pubDate>Thu, 28 Feb 2008 12:00:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.je2050.de/2008/02/28/flex-compiler-open-source-the-logical-consequences/#comment-56436</guid>
		<description>Hey,

it is very nice to see someone do this but actually it is a totally different project and I also do not like eval() at all because it is bad practice in my opinion.</description>
		<content:encoded><![CDATA[<p>Hey,</p>
<p>it is very nice to see someone do this but actually it is a totally different project and I also do not like eval() at all because it is bad practice in my opinion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mem's</title>
		<link>http://blog.joa-ebert.com/2008/02/28/flex-compiler-open-source-the-logical-consequences/comment-page-1/#comment-56435</link>
		<dc:creator>Mem's</dc:creator>
		<pubDate>Thu, 28 Feb 2008 11:37:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.je2050.de/2008/02/28/flex-compiler-open-source-the-logical-consequences/#comment-56435</guid>
		<description>Metal Hurlant have already partialy implement in Actionscript the Tamarin project.

http://metal.hurlant.com/blog/2008/01/02/flash/eval-and-actionscript/

Maybe you can work on it together ?</description>
		<content:encoded><![CDATA[<p>Metal Hurlant have already partialy implement in Actionscript the Tamarin project.</p>
<p><a href="http://metal.hurlant.com/blog/2008/01/02/flash/eval-and-actionscript/" rel="nofollow">http://metal.hurlant.com/blog/2008/01/02/flash/eval-and-actionscript/</a></p>
<p>Maybe you can work on it together ?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

