On (25/11/07 15:13), Stéphane Ducasse wrote:
From: Stéphane Ducasse stephane.ducasse@univ-savoie.fr To: Related to the development of Moose and other related tools moose-dev@iam.unibe.ch Subject: [Moose-dev] Re: About a reference plugin Date: Sun, 25 Nov 2007 15:13:47 +0100
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 :)
Stef
On 25 nov. 07, at 13:51, Tudor Girba wrote:
In the latest FAMIX proposed by Adrian, Package and Namespaces are both ScopedEntities. The reason for this is exactly to not clone the code in both namespace and in package.
I am not sure that I like that though because the semantics of Package is not the one of Scoped.
Doru
On Nov 25, 2007, at 1:39 PM, stephane ducasse wrote:
Hi
I'm about to write a new package reference plugin for moose. Now I have to pay attention because of the way namespaces and packages are orthogonal in Smalltalk. I have a question: when we will be loading java code in Moose what will be a Java package? a moose namespace or a moose package?
If this is a namespace then I will have certainly to duplicate the logic in package and namespace and I would like to avoid that. Does anybody have an idea how to avoid that?
Stef _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com www.tudorgirba.com/blog
"It's not how it is, it is how we see it."
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