flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erik de Bruin <e...@ixsoftware.nl>
Subject Re: [FalconJS] concepts
Date Thu, 29 Nov 2012 07:45:52 GMT
> That said, because we are cross compiling AS, does the classic route support
> as many features of AS, especially the reflection-oriented features?  We
> want to try to compile business logic untouched and it might be using "is",
> "in", "instanceof", etc.  Resig's blog seems to indicate that support for
> instanceOf was important and required all of that code.

Well, there is the JavaScript operator "instanceof", what's wrong with that?

Stuff like 'is', 'as' and 'in' we'll need to syntactically work
around, just like we do with class creation, constructors etc., no big
deal, the compiler should be able to take care of that.

As to classic vs. other routes, a final thought: while bare bones
performance might favour one over the other, we also have to take into
account that probably 99% of performance gain or loss will be due to
feature implementation, not the way we choose to implement a specific
language feature (inheritance, class creation etc.). Also, things like
easy of coding and maintenance are major factors.

Having said all that, I think the bottom line is that there is already
a lot of work done to make the current solution happen. I have looked
at it in dept yesterday and can't find any major fault, although some
of the design decisions might not have been my own. Then again, I
don't know all the considerations that went into it, nor am I familiar
with the limitations (if any) of the compiler. I am happy with take
the current solution forward instead of starting from scratch.


Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

View raw message