Abstract
Macros can provide an important assembly language feature which makes the power of assembly language when multiple levels of nesting are permitted, comparable to that of procedure oriented languages. The problem with macros is that each time one is invoked, it produces a considerable amount of code when anything complicated is done. To retain the power of the macro while at the same time eliminating most of the space consuming property, closed subroutines are nested within the macro. A minimum amount of code is required for the closed subroutine, specifically its calling sequence and housekeeping functions. It is possible to reduce the length of code for the macro which is necessary in the caller's control section by moving the closed subroutine to an entirely different control section. These functions taken together enable the assembly language programmer to keep his modules compact so that a minimum of base register, allocation and manipulation is required.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
