Great, Wolfgang!
But surely, if you have something on the stack youd like to keep, you
still need to save the stack pointer, otherwise how will the system know?
Per
On 09/06/2018 06:50, Wolf via Ql-Users wrote:
Hi,
I'll amend the documentation. I will also mention that this vector,
under SMSQ/E, simply does nothing when called from a compiled
program. I already added a note that under SMSQ/E it is not
necessary to save the stack pointer in BV_RIP(A6) before calling
this vector.
There are also other additions/corrections to the documentaton.
I'll release the new doc either today or tomorrow.
Wolfgang
On 08/06/2018 19:29, pjwitte via Ql-Users wrote:
Having gone through it all again, Ive come to the conclusion that
the bugs are in the documentation! This is what it should look like:
||Vector $11A Reserve Room on Arithmetic Stack QA.RESRI
Call parameters Return parameters
D1.L Number of bytes required D1 ???
D2 D2.L ???
D3 D3.L ???
A0 A0 Preserved
A1 A1 ???
A2 A2 Preserved
A3 A3 Preserved
Error returns: none
In other words, in the case of insufficient memory this routine
returns to a higher level; it never comes back here. There is no
need, in fact it is a mistake, to test d0 on return from this routine.
If anyone knows otherwise then please let ut know!
Per
_______________________________________________
QL-Users Mailing List
_______________________________________________
QL-Users Mailing List
_______________________________________________
QL-Users Mailing List
