> MTASC will get developed by the community to support > AS3 and will continue to be used on a large scale.
I don't think it's that simple. For a start, I don't believe many in the Flash community know much about writing compilers or using OCaml. Ralf is the only one I am aware of who did any modifications to the MTASC source, and he already said he doesn't think he could do it. Also, it will probably take a while for Macromedia/Adobe to release the specifications for the new bytecode, so to keep the current momentum we would have to reverse engineer it. mark On 10/24/05, jtgxbass <[EMAIL PROTECTED]> wrote: > MTASC just wouldnt be where it is if it wasnt an improved AS2 > compiler. The only incompatibilities are where the MM compiler is > basicaly lax/broken, so code designed for MTASC *will* compile in MM > compiler. > I dont think I'm alone in stating that code I develop commercialy for > Flash *has* to be compilable in MM, and hence a new language just isnt > going to work for me. Sure I would like a better language than AS2/3, > but when your hired to do AS work, you cant deliver anything other > than AS. > > So where do we go from here? Simple - NC will develop his new language > - which for the large part will probably be great, but few people will > use it seriously. MTASC will get developed by the community to support > AS3 and will continue to be used on a large scale. > > On NC's decision to develop this new language... as far as flash > specificaly is concerned - I cant see the point. AS3 is a huge > improvemnet to AS2 (as AS2 was to AS1) and I cant see MM taking it in > any other direction in the near future. -- http://snafoo.org/ jabber: [EMAIL PROTECTED] _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
