> Danny Kodicek wrote: > > It's a shame: My object structure has a bunch of objects in a tree > > structure, all of which inherit the same base class. I'd > like them all > > to have a reference to the top-level node object, but I > have to refer > > to it as an Object instead of its actual class name because > otherwise > > it can't compile. > > > You are mixing Classes and Instances. Classes inherit > properties and methods from other classes. > How the instances are linked together at execution time is > another matter.
Well, not really. I may use the words 'class' and 'object' interchangeably on occasion, but I'm quite aware of the distinction. Classes have properties, instances give those properties values, classes define the kinds of data those values can take. I don't think my example is that odd, really. It seems unnecessarily restrictive not to be able to refer to a superclass within a subclass - that's enforcing an arbitrary design principle. Danny _______________________________________________ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
