[haXe] HAXE and MMcomponents V2

[Zjnue Brzavi]

sounding very interesting! please don't stop....

On 9/15/06, Asger Ottar Alstrup <asger at area9.dk> wrote:
> Yes, you would need to adapt the ActionScript code to the library where
> there are differences.
>
> But there are many advantages: for instance, Flash9 support would be within
> reach for ActionScript2. So, porting something like ASwing to Flash9 would
> be simpler than a total rewrite which a true haXe port is: It would much
> more correspond to porting from ActionScript2 to ActionScript3.
>
> Also, it would allow a smoother transition of a large body of ActionScript
> syntax code to haXe. Basically, you could convert one file at a time and
> have some parts in ActionScript syntax and other parts in haXe - until
> everything is converted to haXe syntax.
>
> Another advantage would be that type inference and other haXe semantic
> features could become available in ActionScript syntax.
>
> How different is the AST after parsing in MTASC and haXe? I suspect they are
> pretty similar, so maybe it is so easy that it is worth it just as an
> experiment.
>
> Regards,
> Asger
>
>
> On 9/15/06, Nicolas Cannasse <ncannasse at motion-twin.com> wrote:
> > >     Yes I'm considering this for next MTASC version, which is not planed
> > >     yet.
> > >
> > >
> > > What about the other way? Plug the parser from MTASC into haXe as a new
> > > front-end.
> >
> > Uhm.
> > That would make things blurry. Especially since standard libraries have
> > some differences between MTASC and haXe.
> >
>
>
> --
> haXe - an open source web programming language
> http://haxe.org
>
>