[Info-vax] [OT?] Should compiler warnings be treated as errors ?

[hb]

On 9/10/21 4:17 AM, John Reagan wrote:
> On Thursday, September 9, 2021 at 8:30:16 PM UTC-4, Craig A. Berry wrote:
> 
>>
>> I still routinely see warnings with the ancient DEC/CPQ/HP/HPE/VSI C 
>> compiler for code that produces no warnings with current gcc and clang. 
>> And of course compiler warnings get escalated to linker errors on VMS, 
>> so what Linux is considering now has effectively already been the case 
>> on VMS for a few decades.
> 
> Linker warnings.
> 
> And you can clear that with SET IMAGE /SUCCESS
> 

John already answered, but I've seen this so many times, so I'll expand
on that. They get escalated to linker warnings, not errors. The linker
produces an image file. You will not get one if the linker encounters an
error. And the image activator will active the image without printing
any message, no matter if it is a main image or a shareable. Only if you
try to find a symbol in the image file with lib$find_image_symbol you
will get a warning: %LIB-W-EOMWARN. Yes, a %LIB not a %SYSTEM.

And you can restore any cleared warning with SET IMAGE /RESTORE.