??? 03/30/08 20:43 Read: times |
#152721 - Good implementation Responding to: ???'s previous message |
Michael Karas said:
One technique I have used from time to time is the concept of "inlining" parameter(s) such as a string pointer as shown in following subroutine: Yep, I've used that too for exactly the same purposes. Rather than loading DPTR with the location of a string to send, etc. you can just call the routine with the standard being that the string immediately follows the originating call. But regarding the original request, I'm trying to imagine a situation where you'd want to call a subroutine and then not return from it. Regards, Craig Steiner |
Topic | Author | Date |
call routine problem | 01/01/70 00:00 | |
Yes, but... | 01/01/70 00:00 | |
call routine | 01/01/70 00:00 | |
what do you mean by "come out"? | 01/01/70 00:00 | |
call routine | 01/01/70 00:00 | |
Does not ignore RET but... | 01/01/70 00:00 | |
Good implementation | 01/01/70 00:00 | |
one of the reasons might be... | 01/01/70 00:00 | |
call routine | 01/01/70 00:00 | |
please explain... | 01/01/70 00:00 | |
Two things need explaining | 01/01/70 00:00 | |
Processor doesn't just ignore instructions! | 01/01/70 00:00 | |
I guess ... | 01/01/70 00:00 | |
call routine | 01/01/70 00:00 | |
use sjmp ljmp ajmp![]() | 01/01/70 00:00 |