[Info-vax] VAX Macro to C conversion

[Bill Gunshannon]

On 7/11/19 9:28 PM, Andrew Shaw wrote:
> On Friday, July 12, 2019 at 11:18:03 AM UTC+10, Bill Gunshannon wrote:
>>
>> Lint used to point
>> out a lot of potential problems but I knew few people other
>> than myself who ever actually used it.  If the compiler
>> lets it bad code will continue to come out of the mill.
> 
> I almost always use lint or I add more picky flags to whatever compiler I am using when building something that needs to run in a Production environment.
> I want to explore as many avenues of potential failure as I can before I deploy
> my code as I've already had way too many alarms go off at 3am (I don't know
> whose law it is that says that code will only break at the most inconvenient time.) I still have nightmares of my pager (pre mobile phone era) going off at 3am meaning I had an hour to investigate and fix some anomalous ACMS runtime issue.
> 
> I want my code to break in Dev before I send it anywhere. I don't always get that !
> 

Congratulation.  Welcome to a very select and small group.

Try taking some piece of serious piece freeware and turn on
all warnings before running make.  Then come back and tell
me how much you would trust it.  Someone here is working
on PERL.  Give that one a try.  :-)

bill