Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <20120105063405.14127a2yud0uvbn1@www.teotigraphix.com>
Date: Thu, 05 Jan 2012 06:34:05 -0500
From: Michael Schmalle <mike@teotigraphix.com>
To: flex-dev@incubator.apache.org
Subject: Re: Falcon compiler source code / Falcon architecture
References: 
 <CA+67v5-g802jPgcrZTAYtYyM4jGarrt0=AEx2TVBNaK8_WMfrw@mail.gmail.com>
In-Reply-To: 
 <CA+67v5-g802jPgcrZTAYtYyM4jGarrt0=AEx2TVBNaK8_WMfrw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=UTF-8;
 DelSp="Yes";
 format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.3.9)


> Is there any documentation available explaining the differences
> between Falcon and the current version of the compiler? Or do you have
> a developer wiki for Falcon which might be shared with us, even if we
> don't have access to the source code, yet.
>
> Does the Falcon team already have an understanding of how much more
> work they want to do before the source code can be shared with Apache?
>
> Raju
>

I am also interested in this and now that I have had time to sleep on it,
I really doubt I will get into any code with the compiler or asdoc before
there is a clear definition with what has changed or something is released.

I'm still not entirly clear on what I would plug into from the out side or
even have the ability to modify to create plugins for the outside.

I would be more interested in a simple explanation of the Falcon architecture
seeing that this was built from the ground up, I'm hoping there was some
thoughtful design put into it's core. :)

Mike