[Info-vax] BASIC and AST routines
VAXman- at SendSpamHere.ORG
VAXman- at SendSpamHere.ORG
Wed Nov 24 19:58:45 EST 2021
In article <snlg1h$jrr$3 at dont-email.me>, Simon Clubley <clubley at remove_me.eisner.decus.org-Earth.UFP> writes:
>On 2021-11-24, Arne Vajhøj <arne at vajhoej.dk> wrote:
>> On 11/24/2021 8:31 AM, Simon Clubley wrote:
>>> On 2021-11-23, VAXman- @SendSpamHere.ORG <VAXman- at SendSpamHere.ORG> wrote:
>>>> In article <snjcd1$9hn$2 at dont-email.me>, Simon Clubley <clubley at remove_me.eisner.decus.org-Earth.UFP> writes:
>>>>> That information is only needed because the lowest supported application
>>>>> language on VMS is Macro-32 and not C (or another comparable low-level
>>>>> language).
>>>>
>>>> You're slinging your BULLSHIT yet again. Macro-32 has no inherent need
>>>> or want to know R0, R1, the PC at AST delivery or the PS/PSL. As I have
>>>> requested previously, if you want to be slinging manure in here, please
>>>> show us your shovel.
>>>
>>> Fine. So why are these architecture-specific registers passed to what
>>> is essentially a callback function in a normal application program
>>> and why do those registers need to be visible from that same callback
>>> function ?
>>
>> So far there has only been one guess: yours - that it is to
>> support applications in Macro-32. And that explanation does
>> not make any sense as Macro-32 applications do not need info
>> that C applications does not.
>>
>
>Not directly, but you might have to manually manage or preserve
>something in Macro-32 that an OS based around a higher-level language
>could handle for you automatically in the code generated by the
>compilers for that OS.
Might? You mean you don't know. Yet, you stated that it's purpose is
because of something lacking in Macro-32. Please, answer the original
question.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
I speak to machines with the voice of humanity.
More information about the Info-vax
mailing list