17 Aug
2010
17 Aug
'10
2:45 p.m.
On 16 août 2010, at 21:07, Tudor Girba wrote:
I think it has plenty to do with code.
I would actually love to have the line number of an invocation or an access. But, I guess
in reality this does not work well because it basically doubles the size of the model in
terms of objects. So, I like the suggestion of Simon.
Do we just override #sourceAnchor or do we change the hierarchy?
Cheers,
Doru
On 16 Aug 2010, at 18:27, Alexandre Bergel wrote:
--
Simon
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'?
Cheers,
Alexandre
On 16 Aug 2010, at 11:47, Simon Denier wrote:
--
www.tudorgirba.com
"Beauty is where we see it."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
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