26 Nov
2007
26 Nov
'07
2:58 p.m.
On 26 nov. 07, at 09:09, Johan Brichau wrote:
Hi all,
In the importer I wrote, I have the following mappings:
* Java packages -> Famix namespaces (Simply because java packages
have control over name scoping).
* Java jar files -> Famix packages (it's the closest thing that
corresponds to any 'packaging' thing in Java).
I think it's strange to map Java packages onto Famix packages..
Just my 2 cents ;-)
Oops. I think that I would like to be much clever and know the
answer. It seems that
I will start to work on package and see how it goes. I have the
impression that from a
scenario point of view, I want to see how a class refer/is referenced
by other classes.
and this also at the level of the packages. so the scoping of the
container is important
now this would push me to put java package into namespace but to
analyse I would like the
inverse.
So please help me.
Stef
Johan
ps: I will be looking at using the existing Eclipse importer directly
from JavaConnect/Penumbra too.
On 25 Nov 2007, at 16:25, Toon Verwaest wrote:
----------------------------
Johan Brichau
johan.brichau(a)uclouvain.be
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I thought
about it and I would like to have
java package -> extracted as package
smalltalk package -> as package
smalltalk namespace -> as namespace
Is it what you had in mind?
I don't necessarily think that package equals namespace in Java
either. There are the same amount of namespaces as packages, but
unlike packages, the namespaces are not nested, right?
Well on the other hand, namespaces are obviously deducable from java
packages, so I guess it makes sense to just have packages and write
code to get the namespace info (which is more or less important
because package belongsTo != namespace belongsTo for java).
What is your opinion about the matter?
@Sandro: get involved , this concerns you too, obviously :)