You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Martin Heidegger <mh...@leichtgewicht.at> on 2012/01/16 13:05:14 UTC

Flexionscript

I am having things I am unclear about related to the AS3 language and 
the flex compiler. Maybe all those questions have already been answered 
(too many news these days to keep up on everything). I hope my questions 
are not too redundant.

AS3 - as far as I understand - is still in the "hands" of Adobe. 
However: Many people are interested in language features, some of these 
issues might be dealt by changing the compiler some might be dealt with 
by changing the AVM. It is my understanding that the AVM will stay in 
Adobes hand(with which I am fine with).

Adobe "can not" change the AS3 language without compiler and IDE 
changes. Also the flex compiler should not fix language problems 
creating some sort of egg-hen problem. If users (like me) are interested 
in language changes, whom should they best be addressed to?

Maybe it would be possible to have some sort of "platform" (mailinglist? 
subject prefix?) for talking about language/compiler issues? Wouldn't it 
be got to have a compiler flag like "-compiler.non-conform=true" or a 
code-name (flexionscript)  to test/implement/experiment with new 
compiler features without breaking the AS3 language (a little like the 
-webkit- prefix in browsers)? Is there something like that?

A question to the the apache flex team members that work at Adobe: Is 
there a workflow for telling the world (compiler, IDE, documentation 
providers) if or when improvements (I assume there will be improvements 
at some point) to AS3 as a language and AVM as a platform will be made? 
After all I assume this is the biggest "contact point" between the Adobe 
and Apache.

AS3 - the language Spec - is not contributed (right?), what about the 
MXML language spec?

sincerely yours
Martin Heidegger

Re: Flexionscript

Posted by Martin Heidegger <mh...@leichtgewicht.at>.
On 17/01/2012 02:01, Omar Gonzalez wrote:
> ..so not sure why so many people want to come and suggest language
> enhancements. I understand we all want improvements to ActionScript 3, but
> that's not what we're doing here. We're here to work on, fix, and improve
> the Flex SDK.
1) People use the mxmlc to compile all sort of AS3 projects, many people 
use nothing else but the mxmlc. If the mxmlc is part of Apache Flex - if 
its source code is maintained by Apache Flex - then naturally people ask 
Apache Flex to change it.
2) As there are changes in the AVM and changes in AS3 the mxmlc compiler 
has to follow those changes. So it is a part of the work here to 
actually improve AS3 as a language. Many small language "bugs" have been 
fixed over the years.

> As far as I understand MXMLC uses the same ActionScript 3
> compiler that the Flash Pro IDE uses,
As fas as I understand Flash Pro uses the mxmlc... I could be wrong though.

> ... should wait until we have that code for the Falcon compilers (Falcon and
> FalconJS).
Falcon and Falcon JS might be nice projects however there is a 
possibility that other compilers, perhaps based on OCAML (hint: haXe 
branch) might show up that are faster than Falcon.

> As far as AS3 language changes go once we receive all compilers... I still
> doubt at that point we will make AS3 language changes since at this point
> we will still be limited to the constraints of the AVM.
You might not as well as many others might not. But: its an open source 
project and there will be issue requests, patches, branches, etc. around 
that topic. So: why not setup a "island" for those
interested to?

Ahh, the most important original questions still open.

yours
Martin

Re: Flexionscript

Posted by Omar Gonzalez <om...@gmail.com>.
Yea I agree with you David, I think once we do get the compilers we can
start assessing what really can be done with them. But do you think its
worth the time and effort to spend on MXMLC when we know that Falcon is
coming down the pipe, and most likely with more possibilities in it to
modify the source languages, both AS3 and MXML?

-omar

RE: Flexionscript

Posted by David Arno <da...@davidarno.org>.
> From: Omar Gonzalez [mailto:omarg.developer@gmail.com] 
> Sent: 16 January 2012 17:02
> Well, to start this is the flex-dev mailing list for the Apache Flex
project... 
> it is not the Apache Flash Runtime and ActionScript 3 language Project... 
> so not sure why so many people want to come and suggest language 
> enhancements. I understand we all want improvements to ActionScript 3, 
> but that's not what we're doing here. 

I couldn't disagree more Omar! :)

Pretty much the only reason I'm here is to play my part in modifying the
compiler: both in terms of the source language and in what it outputs. I
have very little interest in the Flex classes themselves.

Of course I can do little until we get our hands on first the mxmlc and
compc compilers and then the falcon one. In the meantime, I'm enjoying
kicking around ideas on what we are going to do with the compilers when we
get our hands on them.

David.


Re: Flexionscript

Posted by Omar Gonzalez <om...@gmail.com>.
Well, to start this is the flex-dev mailing list for the Apache Flex
project... it is not the Apache Flash Runtime and ActionScript 3 language
Project... so not sure why so many people want to come and suggest language
enhancements. I understand we all want improvements to ActionScript 3, but
that's not what we're doing here. We're here to work on, fix, and improve
the Flex SDK.

As far as MXML goes Adobe has stated their intent on donating the MXMLC
compiler. This has yet to pass legal review I believe, like the actual SDK
source code, and is why we have not yet actually received the compiler code
for MXMLC. As far as I understand MXMLC uses the same ActionScript 3
compiler that the Flash Pro IDE uses, except it handles the parsing and
conversion of MXML code. If and when the MXMLC compiler is donated we
should be able to update how MXML files are handled... however, the Falcon
compiler will also eventually be donated (or at least its been stated as an
intention) and personally I think any changes we attempt to make to MXML
should wait until we have that code for the Falcon compilers (Falcon and
FalconJS).

As far as AS3 language changes go once we receive all compilers... I still
doubt at that point we will make AS3 language changes since at this point
we will still be limited to the constraints of the AVM. And without knowing
what exactly Falcon handles and how its done its hard to say that we'll
even be able to make the most minor aesthetic changes to the AS3 language.

In short, I would suggest we all focus our energy on things that we can
effect in the immediate future and that which should be our main focus, the
Flex SDK. That said, nobody is stopping you from dreaming up a wishlist!

-omar