i only wrote the comment, not the whole article
d

i posted something about this over here
http://greenethumb.com/article/11/global-variables-in-as3

in short, ’static’ is only ’static’ to the current swf and its children; it does not propagate up to the root document. you cannot lazily construct a static (singleton) class instance in a child swf you are dynamically loading: it has to be constructed in the root, otherwise you end up with several different ’static’ instances that don’t know about each other.

more details on my comment here.

It’s my pleasure to discuss with you, too!

Althrough I cant totally agree with the trade off required for the additional flexibility that this class offers

I found this discussion with you refreshing, and I look forward to having more such discussions with you in future

I feel the overwriting problem is inevitable because the intention of _global class is to allow both read and write access to some information in anywhere of the system. It’s a feature of the class to allow variables to be overwritten and there are scenarios overwriting a variable is a why of solving some problems.

I do understand the need for the global class to be a singleton,
but I dont quite get the benefit of making a dynamic singleton class.

From what i know, this implementation goes in the opposite direction of encapsulation

examples of possible problems i see when 2 mutually exclusive subsystems use this class is,
- overwriting of a variable which both subsystems use the same name, but are for different intents
- knowledge of the other subsystem, which by right are exclusive to each other [to avoid the first senario]

your implementation of the global class is interesting in its direction, and I would like to better understand when and why you would use this class instead of a normal singleton.

which is why I asked what “what is the difference between the example implementation above, and the singleton pattern used in AS 3″

I apologise for being unclear in my first post.

It has not to be _global/Global or a separate class. Any static variable in any class can serve the purpose. Since people have already accepted the concept of _global means you can access it everywhere, it would be easier to reuse the concept to elaborate the idea of a static variable.

The example I implemented uses singleton pattern to make sure there’s only one instance of Global. I think it makes sense because it won’t be reliable if there are multiple instances.

personally, i never really liked using “_global” in AS 2,
as I felt it made it harder for others to keep track of the variable due to the variable scope, and that the variable could be accessed without. “_global.” prefix.

Just curious, what is the difference between the example implementation above, and the singleton pattern used in AS 3?