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

[plugh]

On Friday, September 10, 2021 at 12:13:55 PM UTC-7, Craig A. Berry wrote:
> On 9/10/21 12:35 PM, Simon Clubley wrote: 
> > On 2021-09-09, Craig A. Berry <craig... at nospam.mac.com> 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. 
> > 
> > Interesting. Are they "genuine" warnings or nonsense type warnings ?
> Here's one from last week: 
> 
> CC/DECC /Include=[]/Standard=Relaxed_ANSI/Prefix=All/Obj=.obj 
> /NOANSI_ALIAS/float=ieee/ieee=denorm/NAMES=(SHORTENED)/Define=(_USE_STD_STAT=1,"VERSION=""3.16""","XS_VERSION=""3.16""")/Include=([--])/List/Debug/NoOpt 
> BASE64.c /OBJECT=BASE64.obj 
> 
> unsigned char uc = index_64[NATIVE_TO_ASCII(*str++)]; 
> ............................................^ 
> %CC-W-UNDEFVARMOD, In the initializer for uc, the expression 
> "(((sizeof(*str++)==1)||((U64)((*str++)|0))==((U8)(*str++))))" modifies 
> the variable "str" more than once without an intervening sequence point. 
> This behavior is undefined. 
> at line number 360 in file D0:[CRAIG.blead.cpan.MIME-Base64]BASE64.c;1 
> 
> .
.
.
.
Which is like 2 VAX instructions and 3 addressing modes?