Coordination would be helpful, but it is important to understand that the HLASM Group and the statement-level language groups confront different problems: their different option sets reflect different situations.
Finally, the HLASM must decide how to process an operation-field entry. Is it a machine instruction. An assembler instruction? If not, is it the name of an in-line macro definition or one resident in the MACLIB concatenation for the current assembly? If not, error. The statement-level language compilers, on the other hand, need to know what machine instructions may appear in the object modules they generate. For the same source-language construct a compiler may---often does---generate very different machine-instruction sequences for different ARCH values. These two problems are similar in the sense that they have common elements, but they are very different in other ways. John Gilmore, Ashland, MA 01721 - USA ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
