> 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. 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. Fred! ----------------------------------------------------------------- ATTENTION: The information in this electronic mail message is private and confidential, and only intended for the addressee. Should you receive this message by mistake, you are hereby notified that any disclosure, reproduction, distribution or use of this message is strictly prohibited. Please inform the sender by reply transmission and delete the message without copying or opening it. Messages and attachments are scanned for all viruses known. If this message contains password-protected attachments, the files have NOT been scanned for viruses by the ING mail domain. Always scan attachments before opening them. -----------------------------------------------------------------
