Hello,

Johan, thanks for the pointer. I will have a look. In fact, with AspectMaps I can have a hierarchic view (package, classes, methods) of the problems.  It is interesting.

Nicolas, in fact most of these problems are related to the RBSpellingRule. This rule produces a lot of problems and most of them are false positives. I think I should not use it.

Stef, as I said in the previous email, I created a job in Hudson to generate a simple report with smallLint rules for Moose and Pharo. These reports are generated every day with the last version of Moose/Pharo and stored..

Moose report: https://pharo-ic.lille.inria.fr/hudson/view/LintReport/job/LintReportMoose/lastSuccessfulBuild/artifact/Moose-WithLint/AllPackages-Simple.xml

Pharo report: https://pharo-ic.lille.inria.fr/hudson/view/LintReport/job/LintReportPharo1.3/lastSuccessfulBuild/artifact/Pharo-1.3-WithLint/AllPackages-Simple.xml

regards,

On Wed, May 11, 2011 at 11:13 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Yes I think that we should really learn how to evaluate the rules and reconsider the ones having too many false positives.
In fact this is part of the experience
Andre what would be fun is to keep all the results so that we can also see
how we are actually fixing the code and also improving the lint rules.
       Co evolution of rules checking and code :)

Stef

On May 11, 2011, at 10:50 PM, Nicolas Anquetil wrote:

> Nice! (or not very nice actually, but useful)
>
> I t seems a bit strange that all methods of FamixClass, FamixPackages, ... even FamixEntity, are coloured.
> It would be interesting to know what are the rules that are violated.
>
> nicolas
>
> De: "Andre Hora" <andrehoraa@gmail.com>
> À: "Moose-related development" <moose-dev@iam.unibe.ch>, "Marcus Denker" <marcus.denker@inria.fr>
> Envoyé: Mercredi 11 Mai 2011 18:04:21
> Objet: [Moose-dev] DistributionMap and SmallLint rules
>
> Hello,
>
> I just created some visualizations (Marcus's idea) using DistributionMap with SmallLint rules to check how distributed are the lint problems in a class. I enclosed some figures with the distribution for some packages of Moose.
> So, the small boxes represent methods. The red color is a method with more than 3 lint problems, the orange 2 problems, green 1 problem and white no problem.
> We can clearly see a lot of "lint problems" in Famix package. Of course, we have some false-positives mainly for Glamour and Mondrian as we can check in [1].
>
> Btw, I also created a job in Hudson to generate a simple report with smallLint rules in Moose (and Pharo):
> Job: https://pharo-ic.lille.inria.fr/hudson/view/LintReport/job/LintReportMoose
> Report: https://pharo-ic.lille.inria.fr/hudson/view/LintReport/job/LintReportMoose/lastSuccessfulBuild/artifact/Moose-WithLint/AllPackages-Simple.xml
>
> regards,
>
> [1] Lukas Renggli, Stéphane Ducasse, Tudor Gîrba and Oscar Nierstrasz, “Domain-Specific Program Checking,” Proceedings of the 48th International Conference on Objects, Models, Components and Patterns (TOOLS’10)
>
> --
> Andre Hora
>
>
> _______________________________________________
> 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


_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--
Andre Hora