Hi, For me one of the _global biggest problems is that EVERYONE, EVERYWHERE can modify the value of a global variable. There's no private attribute at all.
AND be careful because one Player 6 movie can NOT see global variables of a Player 7 movie. And vicecersa, of course. My 2 cents. Bye! On 1/31/06, Manuel Saint-Victor <[EMAIL PROTECTED]> wrote: > I'm reading about the wrongs of using _global in various books and articles > and blogs but I have used several extensions and resources that I am > confident are well built that seem to be making use of _global. My current > project has some use of _global in the code that I am updating an I m > wondering in which cases I should try to remove those. Is there a > reference that I can read that would educate me on the reasons not to use > _global and even tell me some workarounds that would allow me to safely use > _Global if it's necessary. I'm familiar with the use of the Singleton > pattern but feel as if in some cases I might be better with some _globals. > > One case in particular that I'm considering is for some functions that we > would like to have globally available. Am I better off making them static > functions of a class (like Math.random() etc) > and having people importing the class or just plopping them as functions on > the global timeline? > > Thanks in advance- > > Mani > _______________________________________________ > Flashcoders mailing list > [email protected] > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > -- Zárate _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
