There is (a) "unused code" in the meaning its not used within the flex
framework and there is (b) "unused" code in the meaning that its not
used in the community.
(a) will become more as the sdk gets cleaned up and uses
new/better/faster systems
(b) is always ZERO. Its possible to deprecate methods but the flex
framework has (had?) a too big reach to for anything to be never used.
The big issues with the flex framework (from a as3 dev perspective) are
the dependencies everywhere. Not just classes but also methods. Just
take MatrixUtil for example: tons of methods. If we now need but one of
them all of them get added to the swc - bloating the resulting swf size
totally.
However: This kind of "spring-cleaning" is just possible with a unit
testing system up and running.
yours
Martin.
On 17/01/2012 06:06, Alex Harui wrote:
On 1/16/12 12:45 PM, "Iwo Banaś"<banas....@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).
