16 Aug
2010
16 Aug
'10
11:05 p.m.
On 16 août 2010, at 18:27, Alexandre Bergel wrote:
Indeed. It looks strange to me as well. As said in its
class comment, FAMIXAssociation is about linking two famix entities. It has no much to do
with source.
Side question, by its variables are named 'previous' and 'next'? Why not
'source' and 'target'?
Because there are not 'source' and 'target'.
In theory, previous and next can be used to store the order of associations - in a method
body for example.
if you have foo(). bar().
you could ask the invocation of foo() for the next association, which would be bar().
In practice, no importer import this data so...
Cheers,
Alexandre
On 16 Aug 2010, at 11:47, Simon Denier wrote:
--
Simon
I just noticed that FamixAssociation is a subclass of FamixSourcedEntity and as such,
inherits a sourceAnchor field.
To me, it sounds like we could define FamixAssociation>>sourceAnchor as a
redirection:
FamixAssociation>>sourceAnchor
^ self from sourceAnchor
Indeed, an association is defined by the from side entity.
Is there any practical case where we want to link a dedicated SourceAnchor object to an
Association?
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev