Comments on: A better as3 compiler? The logical consequences that never happened http://blog.controul.com/2009/03/the-logical-consequences-that-never-happened/ Elaborations on flash. Tue, 27 Jul 2010 09:31:06 -0700 hourly 1 http://wordpress.org/?v=3.0 By: hristo http://blog.controul.com/2009/03/the-logical-consequences-that-never-happened/comment-page-1/#comment-6 hristo Tue, 24 Mar 2009 22:31:04 +0000 http://blog.controul.com/?p=67#comment-6 Nicolas, thanks for the quick reply! I'm afraid I'm not the guy for the job though. Among the many reasons, I don't even know where to start from. Still, features such as this will only strengthen the haXe adoption trend; we all know that the Flex SDK will very likely never provide anything similar. Nicolas, thanks for the quick reply! I’m afraid I’m not the guy for the job though. Among the many reasons, I don’t even know where to start from.

Still, features such as this will only strengthen the haXe adoption trend; we all know that the Flex SDK will very likely never provide anything similar.

]]> By: Nicolas http://blog.controul.com/2009/03/the-logical-consequences-that-never-happened/comment-page-1/#comment-5 Nicolas Tue, 24 Mar 2009 22:03:55 +0000 http://blog.controul.com/?p=67#comment-5 Forgot to say : the main issue is that ABC bytecode uses a lot of indexes into global tables, so this is one reason why it's not easy to write inline assembly directly, since you need to update the global tables as well. Forgot to say : the main issue is that ABC bytecode uses a lot of indexes into global tables, so this is one reason why it’s not easy to write inline assembly directly, since you need to update the global tables as well.

]]> By: Nicolas http://blog.controul.com/2009/03/the-logical-consequences-that-never-happened/comment-page-1/#comment-4 Nicolas Tue, 24 Mar 2009 22:02:41 +0000 http://blog.controul.com/?p=67#comment-4 You could write a program in haXe/Neko using the hxformat library that would : a) read a SWF b) do some replacements, for instance replace calls to Asm.myOpcode() by the actual corresponding opcode b) write back the SWF on hard drive This is a bit what Joa was planning to do with AS3C, although much more easy to implement thanks to haXe enums support. You could write a program in haXe/Neko using the hxformat library that would :
a) read a SWF
b) do some replacements, for instance replace calls to Asm.myOpcode() by the actual corresponding opcode
b) write back the SWF on hard drive
This is a bit what Joa was planning to do with AS3C, although much more easy to implement thanks to haXe enums support.

]]>