I don't. That way you can tell at a glance which parts of your code reference the internal stuff (and may be pain points in the future against new framework versions).
-Josh On Mon, Jul 14, 2008 at 11:37 AM, Manu Dhanda <[EMAIL PROTECTED]> wrote: > > Hi guys, > > As I am trying to get into this Flex world, I am coming across to a few > things where I need expertise advice like why and what should be done in an > appropriate way. > > So here is one more question: why one should (not) use the following line > of > code and in what scenario's it could be avoided and how? > > use namespace mx_internal; > > Any comments/guidance would be great. > > Thanks. > -- > View this message in context: > http://www.nabble.com/How-appropriate-is-it-using-mx_internal---tp18436139p18436139.html > Sent from the FlexCoders mailing list archive at Nabble.com. > > > ------------------------------------ > > -- > Flexcoders Mailing List > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Search Archives: > http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups > Links > > > > -- "Therefore, send not to know For whom the bell tolls. It tolls for thee." :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED]
