16 Aug
2010
16 Aug
'10
5:47 p.m.
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
16 Aug
16 Aug
6:27 p.m.
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:
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
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
9:07 p.m.
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.
Cheers,
Doru
On 16 Aug 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'?
Cheers,
Alexandre
On 16 Aug 2010, at 11:47, Simon Denier wrote:
--
www.tudorgirba.com
"Beauty is where we see it."
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
17 Aug
17 Aug
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
2:50 p.m.
I would change sourceAnchor for now.
Doru
On 17 Aug 2010, at 14:45, Simon Denier wrote:
On 16 août 2010, at 21:07, Tudor Girba wrote:
--
www.tudorgirba.com
"Next time you see your life passing by, say 'hi' and get to know her."
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
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev 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
16 Aug
16 Aug
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
5240
days inactive
5241
days old
5 comments
3 participants
participants (3)
-
Alexandre Bergel -
Simon Denier -
Tudor Girba