Re: New VSI blog post

On 7/31/2024 8:42 PM, Arne Vajhøj wrote:

On 7/31/2024 4:44 PM, John Reagan wrote:

On 7/30/2024 7:59 PM, Arne Vajhøj wrote:

All of the above is bad in some ways.
>
Dont't ignore warnings, always include .h in implementing
.c, never use old style declarations without arguments and
don't mix VMS C and Clang C.
>
But bad things has been seen out in the big world.

>
And don't forget that /STANDARD=VAXC will cover up a ton of bad code

 :-(
 Maybe time to add this to the C compiler.
        subroutine revenge
       character*80 std
       character*256 fnm
       integer*4 stdlen, fnmlen
       integer*4 cli$present
       if(iand(cli$present('STANDARD'),1).eq.1) then
         call cli$get_value('STANDARD', std, stdlen)
         if(std(1:stdlen).eq.'VAXC') then
           call cli$get_value('FILE', fnm, fnmlen)
           call lib$delete_file(fnm(1:fnmlen), '.c')
         endif
       end if
       end
 :-) :-) :-)
 My apologies for being in Fortran mood instead of Pascal mood.
 Arne
 

Early on, I wanted to get rid of /STANDARD=VAXC.  It is used on the C modules inside the Macro compiler.  I modified the build script to remove it.  A single module then got over 600 warnings (about 575 due to the same type mismatch that really wasn't a problem).  So I as I tell others: "Put the rock back down and back away slowly"