The point of AS2 is:
- packages
- strong typing
If you are not taking advantage of the first, that is ok. AS1 prototype's
are created in the _global scope, so the 2 can co-exist.
However, AS1 does not use strong typing; basically everything is uncast so
tracking down bugs will be easier in AS2 than AS1. Therefore, if something
goes wrong at runtime, blame the AS1 first.
As far as co-existing, yes, AS2 & AS1 compile down to the same bytecode.
- Original Message -
From: "Boon Chew" <[EMAIL PROTECTED]>
To: "Flashcoders mailing list"
Sent: Tuesday, March 14, 2006 5:29 PM
Subject: [Flashcoders] AS2.0 mingles well AS1.0?
Me and my coworkers are in the process of migrating a large body of old AS
1.0 code to AS 2.0 (finally!). Since it's impossible to rewrite everything
in one fell swoop, we expect that for some time the system will be in a
state in which it's mixed with AS 1.0 and AS 2.0.
Questions we have:
What sort of issues or potential problems should we be watching out for?
What is your experience with AS1.0 code mingling with AS2.0 code? Positive,
Negative?
Do you seen any problems with AS1.0 mixing with AS2.0 code, if we avoid
using any Flash 7 specific API? (since theoretically AS2.0 compiles down to
1.0)
Initially the code will be compiled for Flash 6.0. Do you see any problem
with trying to compile the same code later for Flash 7?
- boon
-
Relax. Yahoo! Mail virus scanning helps detect nasty viruses!
___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
