For you the developer best practice is to
qualify only when you need to. In the MXML code-gen case we fully qualify
because we don’t have enough information to know if we need to avoid a
conflict, so it’s just easier to be verbose.
Matt
From:
[email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Gordon Smith
Sent: Tuesday, February 14, 2006
9:42 AM
To: [email protected]
Subject: RE: [flexcoders] class
signature convention
Best practice is to use fully qualified
class names only when necessary for disambiguation (when the same class name
has been imported from more than one package). So the generated code should
really be
import
mx.containers.TabNavigator;
public class
TEOTabNavigator extends TabNavigator
{
...
}
- Gordon
Hello,
I have noticed from alpha to beta when the class is created, Flex builder now
inserts
public class TEOTabNavigator extends mx.containers.TabNavigator
uses the fully qualified pacakge for the super class.
The question is; is this a new convention, should we do this or is the import
being fully qualified enough of a hint as to where the superclass originates.?
To me, it seems redundent.
Peace, Mike
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
YAHOO! GROUPS LINKS
