It would also be nice if the linker was connected to the 'Organize Imports' command to get ride of the weeds.
As you build a class, sometimes you don't end up using what was imported and you know but its a pain in the ass to find them. Peace, Mike On 1/27/07, JesterXL <[EMAIL PROTECTED]> wrote:
import * == for slackers import a.b.c == for pimp-tastic Flex coders import * allows the compiler to look in the package to find the class it needs. If you don't have *, you have to set it manually. Both will result in the same amount of classes being exported into the SWF, so file size is the same. Readability of the code, however, degrades because you don't know "what" classes are used in the class. Caveat with the above is just because you use import doesn't mean the class is actually exported into the SWF, you have to actually use it, like in a variable defintion for example: import mx.controls.Button; var myC:Button; So, it's presumtious to think just because an import is used that it IS IN FACT used... could be cruft. Devil's Advocate? No, but I'll play the role. * is great when you are learning, and know ahead of time you are about to import a ton of stuff. The same reason *, :Object, and other loose typing things are there (allowing opt-in strict typing as it were) allows you to code faster, and type less. On Jan 27, 2007, at 9:07 PM, Mike Crowe wrote: Hi folks, Any downside of doing an: import * vs. import com.adobe.cairngorm.control.CairngormEventDispatcher; for example? Any reason not to do this? TIA Mike
-- Teoti Graphix http://www.teotigraphix.com Blog - Flex2Components http://www.flex2components.com You can find more by solving the problem then by 'asking the question'.
