----- Original Message ----- From: "Danny Kodicek" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Monday, March 19, 2007 2:36 PM Subject: RE: [Flashcoders] Create an object by name
> > > > I'm still not entirely sure what import actually > > > *does* :) > > > > It tells flash where the class definitions can be found and > > distinguishes between classes of the same name, but different > > packages. > > You know, it occurs to me that import is an astonishingly bad name for this > statement. Poorly named methods and properties can really screw up > understanding, and not just in third party code. Sometimes I think properly > named variables or methods can do half your coding for you. Why is it not > called something else? I can think of three better names immediately: > pointTo, locate or classAt Sounds like three worse names, I'm afraid. Import is really the industry standard here (in other languages besides Actionscript) and it would be bad to move from it. IMHO it's pretty descriptive - you import these classes into your project. On reflection, my description is a bit superficial. Import is dealing with class namespaces and packages (collections of classes). I'd better stop now. Paul > > Danny > > _______________________________________________ > [email protected] > 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 > _______________________________________________ [email protected] 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
