MXMLC and COMPC currently leverage ASC. I believe that Flash Authoring leverages the same ASC. Flash Authoring has no use for MXMLC (at least, the MXML compilation).
I don't understand how the compiler can affect the language. ActionScript and the VM are not being contributed to Apache. It is just the language and runtime we are using right now. IMHO, language evolution is not within the domain of responsibility of this project. If you are wondering what will happen if Adobe changes ActionScript, I assume this project will just react to it. Is that any different than what happens with new versions of Java and other Apache projects? On 1/10/12 8:36 AM, "Matthew Poole" <mattjpo...@gmail.com> wrote: > Have Adobe said it would continue to use compc / mxmlc internally? > > Either way the runtime would still have to support the languages features > added so that limits whats possible. > > On 10 January 2012 16:18, Raju Bitter <rajubit...@googlemail.com> wrote: > >> 2012/1/10 Matthew Poole <mattjpo...@gmail.com>: >>> I dont think it necessarily follows that because the compiler is donated >>> that control over the language is assumed. Though it would be fantastic >> to >>> add some of the languges features that have been added to HaXe... >> I'm not sure if there are other Adobe products generating ActionScript >> code internally. In that case, any language evolution would affect >> those products as well. >> >> Does the Flash authoring tool use the Flex compiler to generate SWFs, >> or is there a custom-compiler integrated into the IDE? >> -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
