There is a typo in my post that rather destroys its value. The line |us_64 . . .
lost its first three characters. It should be |&plus_64 seta BYTE(x'40') --signed single-byte +64 The notion trhat the HLASM should be e On 8/4/14, Bob Rutledge <[email protected]> wrote: > John Gilmore wrote: >> . . . continuing >> >> About the construction >> >> | DC AL1(64) A byte containing the number 64 >> >> I am even less enthusiastic; z/Architecture now supports loading and >> storing single-byte signed binary integers in the same way that it >> supports halfword ones, and "containing the number 64" is thus at best >> ambiguous. Moreover, I have never really liked using AL1 or an LA >> instruction to obtain small unsigned binary constants, although like >> everyone else I have resorted to them on occasion. The assembler's >> BYTE bif is much more flexible. I can write >> lus_64 seta BYTE(x'40') --signed single-byte +64 >> |&minus_64 seta BYTE(x'd0') --signed single-byte -64 > > And I see this as impetus to coerce HLASM itself to perform the conversion > so as > to make the value match the comment. > > Bob > -- John Gilmore, Ashland, MA 01721 - USA
