Type is the superclass for things like Class, Interface and maybe even Trait. A ContainerEntity is the superclass for Namespace, Package, Class, or Method. And all these can contain types. Doru On Jun 13, 2008, at 8:13 PM, Stéphane Ducasse wrote: > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com www.tudorgirba.com/blog "One cannot do more than one can do." _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

The naming scheme is based on the type of what gets in it the instance variable. All ContainerEntities can provide scope for types (e.g., Class). This is the definition of the class. A Namespace, a Method and a Class provides scope for Types.

The only problematic part is Package because it does not provide scope. So, for Package the types iv is too high. And Package already has a childNamedEntities iv. But on the other hand, Package is subclass of ScopingEntity which is subclass of ContainerEntity because of references that can be between any ContainerEntity. So, the position of a Package in the hierarchy is still an open question. Doru On Jun 14, 2008, at 9:39 AM, Stéphane Ducasse wrote: > I do not understand why a namespace or class contain "types" > versus > entities? > > Types is misleading from my point of view. > > what is the commonality between a method types and a package > types? > > How should I interpret that? > > how the types iv is interpreted in the context of each subclass. > > May be the comment may state that some instance variables are just > way > to reuse and as such > make no sense for all the subclass interfaces but are necessary to > implement different interfaces. > > Stef > > On Jun 14, 2008, at 2:16 AM, Tudor Girba wrote: > >> Type is the superclass for things like Class, Interface and maybe >> even >> Trait. >> >> A ContainerEntity is the superclass for Namespace, Package, >> Class, >> or >> Method. And all these can contain types. >> >> Doru >> >> On Jun 13, 2008, at 8:13 PM, Stéphane Ducasse wrote: >> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> -- >> www.tudorgirba.com >> www.tudorgirba.com/blog >> >> "One cannot do more than one can do." >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > -- www.tudorgirba.com www.tudorgirba.com/blog "Problem solving efficiency grows with the abstractness level of problem understanding." _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev