8 Nov
2008
8 Nov
'08
10:01 a.m.
On Nov 8, 2008, at 9:55 AM, Tudor Girba wrote:
The receiver is a NamedEntity right now, but perhaps
it should be
Entity to also enable one to hook in an Expression entity later on.
ok for the moment we keep it simple.
ok should I translate that into
receiver = self, super, localVa, classVar, instVar, Class....
Stef
Doru
On Nov 8, 2008, at 9:02 AM, Stéphane Ducasse wrote:
really
I thought that receivingVariable was only set when it was a variable
and not an expression.
So receiver will only refer to a variable?
Stef
On Nov 8, 2008, at 12:10 AM, Tudor Girba wrote:
--
www.tudorgirba.com
www.tudorgirba.com/blog
"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
The correspondent is
FAMIXInvocation>>receiver.
Cheers,
Doru
On Nov 7, 2008, at 6:17 PM, Simon Denier wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev I'm looking into the SmalltalkMethodVisitor
for Famix3 and in
particular how it builds FamixInvocation entity
However there is a receivingVariable attribute in
Famix2::Invocation,
for which I cant find a substitute in FamixInvocation. How should I
deal with this data?
SmalltalkMethodVisitor>>acceptMessageNode:
(...)
aMessageNode receiver isVariable
ifTrue:
[invocation
setReceivingVariable: (self resolve: aMessageNode receiver
name)].
(...)
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
www.tudorgirba.com/blog
"Every thing has its own flow."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev