I apologize for asking this, as I prefer to find out myself
from empirical test coding. However, since this could
conceivably trash my PB/DOS EXE's, and therefore
my OS, I'd prefer to find out by asking first.
This question, as far as my production usage, would pretty much only
apply to OBJ file subs/functions linked into my main PB/DOS EXE's.
In a thread in the Programming Forum, Mr. Paul Dixon used a technique I had
never seen before to allocate a local storage buffer.
To wit:
Could the same method be used to allocate temp storage in subs/functions
used by PB/DOS EXE's? Or is the stack methods of DOS programs too
different from 32-bit programs for it to be used? (naturally, the
DOS procedures would use 16-bit addressing, not 32-bit).
Any assistance gratefully received.
------------------
from empirical test coding. However, since this could
conceivably trash my PB/DOS EXE's, and therefore
my OS, I'd prefer to find out by asking first.
This question, as far as my production usage, would pretty much only
apply to OBJ file subs/functions linked into my main PB/DOS EXE's.
In a thread in the Programming Forum, Mr. Paul Dixon used a technique I had
never seen before to allocate a local storage buffer.
To wit:
Code:
FUNCTION blah-blah (arg&&, arg2&&) AS STRING 'some code ! pushad ! [b]sub esp, 12[/b] ! [b]mov edi, esp[/b] 'main ASM code ! [b]add esp, 12[/b] ! popad 'rest of code END FUNCTION
used by PB/DOS EXE's? Or is the stack methods of DOS programs too
different from 32-bit programs for it to be used? (naturally, the
DOS procedures would use 16-bit addressing, not 32-bit).
Any assistance gratefully received.

------------------
Comment