[Info-vax] VAX Macro to C conversion

Arne Vajhøj arne at vajhoej.dk
Fri Jul 12 20:38:55 EDT 2019


On 7/12/2019 6:37 PM, Stephen Hoffman wrote:
> In different realities, another language is often (usually?) more 
> appropriate than C.  And in some of those realities, wholesale rewrites 
> are even feasible and viable.  But that's not where many of us are right 
> now.  Particularly for VSI, as they've seemingly too few folks on staff 
> for what they need to do, much less for what they want to do. There's 
> always more work than there's available schedule time, which means we're 
> always compromising with what can get shipped and when.
> 
> 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. 

Is C99 to C18 really that important?

When I look at the new features list then the only potentially
interesting items I see are the threads and UTF support.

Arne



More information about the Info-vax mailing list