On Tue, Jan 17, 2012 at 1:31 PM, Fred van der Windt <[email protected]> wrote: >> Having the CLC near the EX helps for cache. I also like to assemble it >> in-line because the right USINGs apply. We noticed that it is >> attractive to run over the CLC (with the length byte 0 as assembled) >> and then EX behind your back to do the real thing. More attractive >> than branch over the target if the instruction lets you. > > The USING-issue is a strong argument in favor of this: I juggle around USINGs > a lot and it is a pain (and error-prone) to set up the same USINGs for a > single instruction that needs to be EXecuted.
Right, I'm more and more tempted to drop all USINGs at the end of subroutines and explicitly state which ones apply upon entry. Since I have nested subroutines with static scope, it's even more appropriate. Within the routine itself, I try to have the USING and DROP at the same nesting level. > We use the HLASM Toolkit Structured Programming Macros which means that we > can't easily insert an instruction 'after' a Jump instruction. Almost all the > Jump instructions are generated by the SPM macros. What's a Jump instruction ;-) Really, mine are only generated by the structured programming macros (including one to exit the routine as part of error handling). Rob
