S
Steve Myres, PE
Actually, you can do this in a SLC in a kind of kludgey, assembly language sort of way. For each reusable subroutine, define fixed memory locations for the arguments and returns. Load your live data into the predefined registers, call the JSR, and fetch the returns from the registers. This is obviously suitable only for subroutines with small lists of arguments and returns or the move time overhead will be prohibitive. It can be done a lot more efficiently if the data is structured suitably. Using the same method, pass a single pointer to data locations, and the subtorutine can work on the real data using indexed or indirect addressing. This eliminates all the MOV or COP statements.
That having been said, I freely admit that function blocks or subroutine calls that accept and return values (like in the CLX or TI505 PGTS command) are much better. Just pointing out what can be done.
Compilable function blocks also hold the potential for encapsulation of proprietary procedures without locking the user out of the whole program, which I see as a plus.
That having been said, I freely admit that function blocks or subroutine calls that accept and return values (like in the CLX or TI505 PGTS command) are much better. Just pointing out what can be done.
Compilable function blocks also hold the potential for encapsulation of proprietary procedures without locking the user out of the whole program, which I see as a plus.
