incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Left Right <>
Subject Re: [jira] [Updated] (FLEX-51) Please check support for ExactValue initializer
Date Wed, 25 Apr 2012 09:16:23 GMT
>  but your example applies to the way
> that mxmlc handles things, right?
> Yes, I don't know how Falcon does it.

To be honest, I feel very uncomfortable knowing that MXML will be parsed by
the compiler together with the AS code for the number of reasons I won't
list here because they might be just superficial.
On the other hand, this very fact is something that we also have to
consider if we want to make changes to MXML grammar now. The above change
was suggested to Adobe about 1-2 years ago, but nothing was done on the
matter. Adobe didn't publish any specification for MXML and they aren't
telling what features will be or are planned to for the MXML that will be
in the new compiler. Suppose we proceed with adding this patch to current
version of mxmlc - and then Adobe comes up with an incompatible compiler -
what than?



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message