Personally I think all "*+n" branches are ugly and dangerous. Inside a macro, I would use a generated label with some prefix and &SYSNDX.
Inside normal assembler, I would generate a real label. However, that being said, I use the HLASM structured assembler macros that solve all these problems for me (in both macro and asm code) : IF (TM,FLAG,BIT,NO) L R15,SOMEVAL ENDIF -----Original Message----- From: IBM Mainframe Assembler List [mailto:[email protected]] On Behalf Of zMan Sent: Thursday, July 2, 2015 9:00 PM To: [email protected] Subject: *+n branches I was raised to do single-instruction branches thus: TM FLAG,BIT Is the flag bit set? BO *+8 Yes, skip next instruction L R15,SOMEVAL No, get the value *+8 DS 0H Yes, of course I realize that the "DS 0H" is meaningless, but it helps readability. My question is whether folks see this as: - useful - common - overly clever - evil ...or what? I've often wished for an assembly option that would note "*+n" branches and warn if they were not skipping one instruction (and doing so *exactly*!). -- zMan -- "I've got a mainframe and I'm not afraid to use it" ================================ Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ +1 800.966.3270 ■ +1 781.577.4321 Unsubscribe From Commercial Email – [email protected] Manage Your Subscription Preferences - http://info.rocketsoftware.com/GlobalSubscriptionManagementEmailFooter_SubscriptionCenter.html Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy ================================ This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. Thank you.
