Hi all
In the smalltalk importer for Famix 3, 'Smalltalk' is considered as a namespace. As a consequence, any method which accesses Smalltalk is tagged as making a FamixReference to the namespace.
Problem is, Cook assumes that any outgoing references made by a method should be a FamixType.
So, what is right? - 'Smalltalk' in a method should be considered as an access to a global variable? - or Cook should be more careful and select only references to FamixType.
-- Simon
Hi all
In the smalltalk importer for Famix 3, 'Smalltalk' is considered as a namespace. As a consequence, any method which accesses Smalltalk is tagged as making a FamixReference to the namespace.
Smalltalk is a global that points to a namespace.
Problem is, Cook assumes that any outgoing references made by a method should be a FamixType.
Why that? In java can you access a namespace? and it is a Type?
So, what is right?
- 'Smalltalk' in a method should be considered as an access to a
global variable?
may be this is the easiest solution
- or Cook should be more careful and select only references to
FamixType.
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On 24 sept. 09, at 21:42, Stéphane Ducasse wrote:
Hi all
In the smalltalk importer for Famix 3, 'Smalltalk' is considered as a namespace. As a consequence, any method which accesses Smalltalk is tagged as making a FamixReference to the namespace.
Smalltalk is a global that points to a namespace.
Problem is, Cook assumes that any outgoing references made by a method should be a FamixType.
Why that? In java can you access a namespace? and it is a Type?
No. Technically you import namespace and then you can reference types inside. But I dont know if we should consider the import as a first- class access itself.
So, what is right?
- 'Smalltalk' in a method should be considered as an access to a
global variable?
may be this is the easiest solution
Yes, we should update the logic of the importer then.
- or Cook should be more careful and select only references to
FamixType.
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
No. Technically you import namespace and then you can reference types inside. But I dont know if we should consider the import as a first-class access itself.
The import should be made a first class entity. It should either be produced from an 'import' statement in a Java file, or automatically infered from the fully qualified type accesses.
Alexandre
-
Alexandre Bergel -
Simon Denier -
Stéphane Ducasse