Hi,
Type is the superclass of Class. In extensions, Type will also be the superclass of Interface and Trait. Maybe you disagree with the name, but the Type class has a purpose.
Ok you mean groups of "signatures"
I am not sure that a group of signature is the only commonality between Interface and Class. We called it a Type, because that is what Class and Interface define.
In a Namespace we can have both Classes and Interfaces, and these all will be in the types collection of the Namespace. I did not say that "in a class I have methods", I said that in a Class I can have other Classes.
Ok I see. All that points should be written down and we should make good interfaces because types for me is just an internal factorisation.
It is, but I think it makes sense.
Now you mention that a method has types? What does it mean?
A Method can contain Classes - means that in Java I can define an anonymous class inside a method.
Doru
Cheers, Doru
On Jun 15, 2008, at 1:37 PM, Stéphane Ducasse wrote:
On Jun 15, 2008, at 11:28 AM, Tudor Girba wrote:
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.
still I do not understand what Types are. In OOP Types are not Classes So in the namespaces I do not have types but classes. in a class I do not have types but methods.
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@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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com www.tudorgirba.com/blog
"Every thing should have the right to be different."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com www.tudorgirba.com/blog
"We cannot reach the flow of things unless we let go."