Hi Mike, This is true, but ASC is already moving to ASNext targeting the next generation runtime which is targeting game developers. So our resources are assigned to that and the time we have to take ASC 2.0 changes to Falcon, are limited. Gordon will bring key/showstopper bugs fixed in ASC 2.0 to Falcon, we cannot commit to anything more.
Just a heads up, given the architecture changes of the next-gen runtime, Flex will not be able to run in it. I would "highly" recommend you guys having a look at Feathers (work from Josh Tynjala - feathersui.com) on top of Starling, which will run beautifully in our next runtime. Some videos: https://vimeo.com/51010861 http://www.youtube.com/watch?v=DGRy7H17MkA&feature=youtu.be&hd=1 Thibault Imbert | sr. product manager gaming (Graphics, Language, VM, Compiler) | Monocle | adobe systems gaming.adobe.com <http://gaming.adobe.com/> | bytearray.org <http://bytearray.org/> | @thibault_imbert On 10/18/12 11:36 AM, "labri...@digitalprimates.net" <labri...@digitalprimates.net> wrote: >>We have no plans keeping ASC 2.0 (and above) in sync with Falcon, as I >>said previously, today the compilers are different projects and >>targeting two different audiences. > >Yeh, we totally get why parsing the AS language and generating bytecode >will be very different for the game market. I can't imagine the amount of >time you guys are spending on the differences in for loops alone.... > >Mike >
