On Thu, Feb 20, 2014 at 3:59 PM, Paul Gilmartin <[email protected]>wrote:
> On 2014-02-20 14:38, Ed Jaffe wrote: > > On 2/20/2014 12:53 PM, Robert Ngan wrote: > >> It'd be nice if macros and instruction operands were handled the same > way, > >> I don't like splitting operand names across lines as it makes searching > for > >> them more difficult so I use zeros as a pad character, e.g. > >> > >> MVC > 0(L'QVSIMGLOGICALPARTITIONNAME,R4),00000000000000000000+* > >> QVSIMGLOGICALPARTITIONNAME Move out the LPAR name > > > > Clever. There is no limit to how many zeros can appear? > > > If there is, you can break it into 000+000+000+... until you encounter > whatever limit on expression complexity exists. > > And, I believe a '0' in column 72 can serve as a continuation indicator, > so if the '+' appears in column 16 of the next line there's no problem > if the zeroes overflow slightly into 73-80. > > None of which excuses the "High" Level Assembler for carrying > lexical restrictions rooted in the 1960s into the 21st Century. > How much time do programmers waste fighting this stuff? > > -- gil > That's why I really like FLOWASM. Let it worry about the idiosyncrasies of the HLASM parser's love of 80 column cards. -- Wasn't there something about a PASCAL programmer knowing the value of everything and the Wirth of nothing? Maranatha! <>< John McKown
