Right... but for the CL, you want F-word alignment anyway, although it would only cause a trivial warning if it wasn't.
As for the "oh-so-clever" remark, it only meant reusing an adcon as the branch target... it's a very minor point; I'd just prefer something like B *+1 or EX Rx,* that more clearly doesn't look like an accident. OTOH, it's not as easy if you have no code-base. It is very true that anything is better than a wild branch. sas On Mon, May 3, 2021 at 8:00 PM Tony Thigpen <[email protected]> wrote: > Thanks for the alignment issue. I went back and found that a DS 0H was > in the code in some historical copies of the macro, but not in all the > copies. I must have fat-fingered a line delete at some point. > > Also, the SOC1 is only if I did not tell the macro how to handle a bad > value. With some of my code, I am just too deep in the levels and past > all other edits. So, as such, there should "never" be a bad value. So, > instead of having to set up a new message or returning up the code > levels, I want an abend so I can actually review the dump and see what > happened. > > I know too many programmers that say "it will never happen" and so don't > put some sort of trap in "just in case". Eventually, they will get burnt. > > Many years ago, there was a piece of software that put out a message: > "Call Joe at xxxxx and tell him he owes Bob $10". Bob had bet Joe that > some condition could never occur, but it did. Bob got his $10. :-) > > Tony Thigpen > >
