[Info-vax] VAX Macro to C conversion

Michael Moroney moroney at world.std.spaamtrap.com
Tue Jul 9 00:15:46 EDT 2019


Simon Clubley <clubley at remove_me.eisner.decus.org-Earth.UFP> writes:

>On 2019-07-08, Michael Moroney <moroney at world.std.spaamtrap.com> wrote:
>> seasoned_geek <roland at logikalsolutions.com> writes:
>>
>>>On Monday, June 24, 2019 at 7:39:07 AM UTC-5, Simon Clubley wrote:
>>>> 
>>>> How much work would be involved in a rewrite of the shadowing code in C ?
>>>> 
>>
>>>Careful there. You are forgetting the C compiler is roughly 2 decades behind in 
>>>standards and capabilities.
>>
>> Out-of-date C compilers would be the least of the problems with such a
>> rewrite.

>Yes, but if you were implementing something like this from scratch
>these days, you would use C instead of Macro-32 simply because of
>all the major advantages C brings you, even with an old compiler.

My comment was regarding how truly evil the Macro-32 shadowing code is, not the
merits of conversion of Macro to C or anything else.

New or significantly rewritten VMS code for x86 is almost always in C, with the
exception of extremely specific code is in x86 assembler like SWIS/interrupt code.



More information about the Info-vax mailing list