OverviewPyramid metrics

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

OverviewPyramid metrics

Stephan Eggermont-3
I wonder about this calculation:

nop := aMooseModel allModelNamespaces size.

When I run it on all Glamour packages, I get:
Instead of the 21 packages

Stephan

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: OverviewPyramid metrics

Tudor Girba-2
Indeed. For Pharo models, we should ideally run it on allModelPackages.

Cheers,
Doru

On Sun, Oct 5, 2014 at 8:01 PM, Stephan Eggermont <[hidden email]> wrote:
I wonder about this calculation:

nop := aMooseModel allModelNamespaces size.

When I run it on all Glamour packages, I get:
Instead of the 21 packages

Stephan

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev




--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: OverviewPyramid metrics

Stephan Eggermont-3
In reply to this post by Stephan Eggermont-3
Doru wrote:
>Indeed. For Pharo models, we should ideally run it on allModelPackages.

When would allModelNamespaces be the correct one?
For java projects, I get an off-by-one (1 extra package for
unpackaged classes).

Stephan
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev