Re: Make specific warning error with gnat?

[BrianG <briang000@gmail.com>]

Stephen Leake wrote:
> Markus Schoepflin <nospam@no.spam> writes:
>> Am 02.07.2010 11:30, schrieb Stephen Leake:
>>> Markus Schoepflin<nospam@no.spam>  writes:
>>> gnat is a very good compiler; the warnings it produces should be taken
>>> seriously.
>> I would love to, but I'm dealing with a multi-million LOC legacy code
>> base of Ada 83 in maintenance mode, which produces quite a large
>> number of warnings.
>>
>> I neither have the time nor the resources available to fix all of
>> them, nor am I allowed to do so. 
> 
> I can understand not changing design in a maintenance situation, but
> adding 'pragma Warnings (off)' in places ought to be ok. Still, it can
> be a lot of work.
> 
In many maintenance situations, _ANY_ source code change is an issue. 
The more files you change (in some situations the more lines you 
change), the greater the impact - on testing and on cost.  Adding 
pragmas throughout the code may be as large an impact as a 
moderate-to-large redesign.

Another GNAT warning I'd put in the same category is 'object XYZ is read 
but never written' (or something similar).  I saw this recently for a 
record type (defined in a different location), where all components have 
default value ... except for one which was added recently.