|
> If the external entry point is first the code works fine. Is there some > API option I missed which protects one from calling externally an > INTernal entry point? > I think so, and it must be so. The return from an INTernal entry point is via an instruction pointer, while the return from an EXTernal entry point is via the RTX instruction. Only the latter returns to a different program on the invocation stack. Now, there is nothing that technically prohibits doing what you want and it might be a wonderful thing to have, but the architecture forbids it. As well as security considerations.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
