Hi Simon,
A long time ago, we decided that isStub should reflect exactly the intention of an analyst of including that entity or not.
So, the interpretation would be that if we choose to import an explicit package A, then all packages that extend the classes from A should be stub packages. If we choose the classes in A then all the packages that extend these classes will not be stub.
If more semantics are wanted, we could have other properties, like isDerivedAsStub (bad name :)).
Maybe an idea would be to add an option in the importing context to allow us to specify what kind of strategy we would want for isStub.
Cheers, Doru
On 14 Jan 2010, at 13:23, Simon Denier wrote:
Hi there
I would like your opinion on Issue 287: allModelPackages does not retrieve pure extension packages
One proposed solution is to set the isStub flag on package/namespace imported because of stub classes (i.e., not specifically requested by the user). For now, this is a smalltalk specific problem. However, it would be good if the semantic is clearly agreed between the importers.
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Problem solving efficiency grows with the abstractness level of problem understanding."