Mine is always indented and I always include a +x for each instruction
so that if an instruction is changed, they don't have to recalculate the
branch, just update the positional length:
CLC IPRPLPT,FULL0
BNE *+4+6
MVC IPRPLPT,EZRP_BIND_PORT
MVC IPRPFIP6,NAMEV6_IP
CLC IPRPFIP6,QUAD0
BNE *+4+6
MVC IPRPFIP6,EZRP_BIND_IPV6
CLC V4ASV6_ADDR(12),IPRPFIP6
+ LTR R15,R15
+ BNZ *+4+6+4
+ CLC EZSI_APITYPE,=H'3'
+ BE ERRNO_30309
Very easy to spot and much more readable than a "IF" construct.
Tony Thigpen
-----Original Message -----
From: Phil Smith III
Sent: 12/04/2013 06:16 PM
Tony Thigpen wrote:
I try to balance the use of B *+2+4 style branches against the
cluttering up by using a bunch of labels. It's never for more than 2
instructions.
I done got larned on me pappy's knee not to do it for more than ONE
instruction, and to use something like:
BE *+8 Some comment
LA R1,1(,R1) Some other comment
*+8 DS 0H
It's cutesy but I find it quite readable. YMMV.
.phsiii
