On 2/24/12 1:04 AM, "Martin Heidegger" <m...@leichtgewicht.at> wrote:
>
> The proposal would make it easier to integrate version numbers but its
> the version numbers
> themselves that are a problem, included by "include" or build process or
> that new compiler feature.
What is the problem?
>
> What is the current workflow to test these version numbers? Obviously
> all classes of a swc will be
> invalidated right now on every release (even without changes at all)
We don't have to test since there is an include.
>
> All those version numbers are noise that bloats the swf size,
> documentation and API and results
> in maintenance.
Remember, the string is in the constant pool, so it is one class trait entry
per class.
>
> In the compile process the compiler could lookup each dependency of
> different swcs. If they have the same
> md5 hash he just uses the first one. If the md5 hashes differ it checks
> if the version compatibility (if available).
>
I think I still care about mismatches when loading SWFs as well, so not just
compile time.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
