[Info-vax] VAX Macro to C conversion

[Craig A. Berry]

On 7/12/19 5:37 PM, Stephen Hoffman wrote:
> Most of us working with OpenVMS are in a reality where use of C remains 
> endemic on OpenVMS, and where something approaching half of all the 
> source code present in OpenVMS is written in C, and yes, where C is 
> problematic and for various reasons.  That means VSI and many of us are 
> using C and maybe C++.  And it means we'll be looking toward using 
> C17/C18/C11 and features well beyond the not-really-C99 available at 
> present on on OpenVMS. And we will (hopefully) see the integration of 
> the address sanitizer, safe-stack, and/or various other LLVM-based tools 
> including fuzzing tools, as well as the advent of mechanisms that'll 
> help guide C developers toward better coding practices and better APIs.

Getting the parts of the OS that have already been written or re-written
in C up to snuff to be compiled under clang will likely be no small
project.  I hope I'm wrong, but I wouldn't expect to see ASAN or other
such tools in the GEM-alike backward-compatible compilers.  Can one even
build VMS itself currently without the use of /STANDARD=VAXC?