From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00
	autolearn=unavailable autolearn_force=no version=3.4.4
X-Received: by 10.107.26.10 with SMTP id a10mr2724076ioa.57.1478341700616;
        Sat, 05 Nov 2016 03:28:20 -0700 (PDT)
X-Received: by 10.157.54.141 with SMTP id h13mr2092342otc.20.1478341700588;
 Sat, 05 Nov 2016 03:28:20 -0700 (PDT)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!news.glorb.com!q124no383633itd.0!news-out.google.com!i74ni663itb.0!nntp.google.com!e187no385354itc.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Sat, 5 Nov 2016 03:28:20 -0700 (PDT)
In-Reply-To: <nvflgf$b00$1@dont-email.me>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=79.182.0.48;
 posting-account=gqw3dgoAAAC1n0FUnjZEhXcW3umVS9pY
NNTP-Posting-Host: 79.182.0.48
References: <nvflgf$b00$1@dont-email.me>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <0ff97519-ae71-4c27-8654-b6eab0ca4f96@googlegroups.com>
Subject: Re: [Ann] AdaControl 1.18r8 released
From: artium@nihamkin.com
Injection-Date: Sat, 05 Nov 2016 10:28:20 +0000
Content-Type: text/plain; charset=UTF-8
Xref: news.eternal-september.org comp.lang.ada:32250
Date: 2016-11-05T03:28:20-07:00
List-Id: <comp.lang.ada>

Thank you for the update and the work you do.

I would like to raise an issue with static analysis tools, style checkers and similar tools that is particularly valid for tools aiming at Ada projects.

Sometimes a developer decides to try these tools on an already existing codebase. This will lead to thouthands of violations.

Fixing them is not acceptable in a field tested code.

The developer would like to know only about the violations in the newly added code.

Allowing this requires integration with source control tools and the ability to parse the analysis tool's log in a smart way (for example adding a line of code in the beginning of the file, will cause all the lines of the violations to increase by one)


It is interesting to hear your thoughts about this, and if you are aware of any solutions used by AdaControl users.



On Thursday, November 3, 2016 at 5:36:11 PM UTC+2, J-P. Rosen wrote:
> A new version of AdaControl has been released at the usual place:
> http://www.adalog.fr/en/adacontrol.html
> 
> The count goes up to 68 rules and 532 subrules!
> Most awaited, AdaControl accepts now directly .gpr files, and the
> executable versions use Gnat-GPL2016.
> See the file HISTORY for a detailed list of new features.
> 
> Enjoy!
> 
> -- 
> J-P. Rosen
> Adalog
> 2 rue du Docteur Lombard, 92441 Issy-les-Moulineaux CEDEX
> Tel: +33 1 45 29 21 52, Fax: +33 1 45 29 25 00
> http://www.adalog.fr