[Info-vax] Creating an open source version of VMS, was: Re: OpenVMS Hobbyist Notification

[Simon Clubley]

On 2020-03-12, Arne Vajhøj <arne at vajhoej.dk> wrote:
> On 3/12/2020 5:25 PM, Simon Clubley wrote:
>> 
>> You are either being deliberately obtuse or you simply do not
>> understand what I am saying.
>> 
>> To answer your question: the abstraction comes from how addresses
>> are referenced in C source code versus how they are referenced
>> in Macro-32.
>
> Since you showed two pieces of C code, then I was obvious searching
> in the C code on VMS.
>
> It did not occur to me that you were describing Macro-32 with C examples.
>

I am not. The problems originate from the need to support Macro-32
when calling VMS APIs but they infect other languages on VMS equally badly.

If you could write VMS API code which used C style (or other higher
language code) addressing to their full ability, you could simply
write something like /mode=64_bit on your compile and link commands
and be done with it.

You can't do that on VMS due to the way the VMS APIs are structured.

> I think you will find that if you want to make a point about a problem
> you see in language X then it may facilitate better communication if
> your code example actually is in language X.
>

????

The problems are not language specific and the problems are equally
the same on VMS regardless of language, including in C.

You can no more switch to using RMS in some transparent 64-bit mode
in C or Fortran than you can in Macro-32.

Simon.

-- 
Simon Clubley, clubley at remove_me.eisner.decus.org-Earth.UFP
Walking destinations on a map are further away than they appear.