I tested this:
package {
public class MyClass {
private static var instNum:Number = 0;
public var someObj:Object = new Object();
public function MyClass() {
someObj.name = "Sun" + MyClass.instNum++;
}
}
}
and tracing later gives:
var mc1:MyClass = new MyClass();
var mc2:MyClass = new MyClass();
trace("mc1.someObj.name: " + mc1.someObj.name); //outputs mc1.someObj.name: Sun0
trace("mc2.someObj.name: " + mc2.someObj.name); //outputs mc1.someObj.name: Sun1
trace("mc1.someObj.name: " + mc1.someObj.name); //outputs mc1.someObj.name: Sun0
trace("mc2.someObj.name: " + mc2.someObj.name); //outputs mc1.someObj.name: Sun1
... so seems to give two separate objects, one for each instance. But
perhaps issues would appear in sub classes. I don't know.
g
Tuesday, February 09, 2010 (3:36:30 PM) Henrik Andersson wrote:
> Allow me to explain why it is bad. It is due to the object only being
> created once. Not once per instance of the class, but once total. This
> is clearly going to cause issues for any class that is used more than once.
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
