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: domain of aharui@adobe.com designates
 64.18.1.185 as permitted sender)
From: Alex Harui <aharui@adobe.com>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>,
        "flex@rduartes.net" <flex@rduartes.net>
Date: Mon, 16 Jan 2012 13:06:12 -0800
Subject: Re: Flex "code cleanup"?
Thread-Topic: Flex "code cleanup"?
Thread-Index: AczUj9rWl8q0Y/nSQZKxq8CC5c0N9QAAtIvj
Message-ID: <CB39D144.3A2A5%aharui@adobe.com>
In-Reply-To: 
 <CAD0VuCJ358+6216SfRNJ5gSAYQzYZF0cS+i+N4veW5Po++0qSw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0


On 1/16/12 12:45 PM, "Iwo Bana=B6" <banas.iwo@gmail.com> wrote:

> I don't think there will be that much unused code. The bigger issue is
> that there is a lot of code which is executed unnecessarily. (Doug
> pointed this in the other thread)
I agree, although in any one particular app there is much more unused code.
That is why a more granular, composition-based implementation should be
beneficial (and potentially solve the backward compatibility problem as
well).
--=20
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui