Quoting Erik de Bruin :
Mike,
I try to talk about FalconJx, as I believe you call your "version" of
the AS -> JS compiler when I talk about your work.
Ok, I understand. I'm trying to stay away from the phrase of "my way".
I just see it as an alternative that I understand. Which means I can
On 12/17/12 10:36 AM, "Erik de Bruin" wrote:
> Mike,
>
> I try to talk about FalconJx, as I believe you call your "version" of
> the AS -> JS compiler when I talk about your work. I refer to FlexJS
> when I talk about the project to allow the user to write in an AS
> based framework (either b
Mike,
I try to talk about FalconJx, as I believe you call your "version" of
the AS -> JS compiler when I talk about your work. I refer to FlexJS
when I talk about the project to allow the user to write in an AS
based framework (either based on Alex's approach or a new one, based
on my experiences
That's a bit up in the air right now I think.
The way I'm writing tests is AS -> JS google closure. But I'm right in
the middle of refactoring the emitter classes.
The tests I'm writing can be run from ant or whatever, just like the
Falcon tests. I just haven't made a build file yet.
Have
Hi,
I'm trying to figure out how to build tests for the AS to JS cross compilation.
Should we write AS "strings" and have a script put those through the
FalconJS/FalconJx compiler and compare the result with a pre-defined
"intermediate JS" result? If so, what would be the best tool to write
those
