27 Mar
2009
27 Mar
'09
11:56 p.m.
Oh... ok...
Thanks for your explanations.
I had a look at the class diagram, but it was still unclear.
Alexandre
On 27 Mar 2009, at 23:47, Tudor Girba wrote:
Hi Alex,
I guess this mail was aimed at moose-dev :)
Have a look here:
http://moose.unibe.ch/docs/famix/famix3.0/classdiagram
NamedEntity>>parentPackage points to the FAMIXPackage.
NamedEntity>>belongsTo
- points to a ContainerEntity and it describes the language scope
(e.g., FAMIXNamespace)
- however, it is derived (that is why in the diagram it appears
with / in front). In this case this means that it will get overriden
in subclasses to point to something else. This is useful for
providing a polymorphic API for getting to an outer language scope
(e.g., from FAMIXClass to FAMIXNamespace)
Type>>container
- points to the container, and it is not derived.
Type>>belongsTo returns self container
Cheers,
Doru
On 27 Mar 2009, at 23:37, Alexandre Bergel wrote:
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Dear List,
What is the difference between NamedEntity>>parentPackage,
NamedEntity>>belongsTo and container ?
I guess one should be for the package, and another one for the
namespace. But a third?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Pharo-project mailing list
Pharo-project(a)lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
--
www.tudorgirba.com
"From an abstract enough point of view, any two things are similar."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev