On 2016-08-23, at 10:21, Ngan, Robert wrote:
> Hmm, there's always something new to learn with the assembler. I've never
> encountered the boundary and offset operands of ORG. That's useful to know
> for future coding.
> The only thing that ORG doesn't do vs. DC is emit the potential filler byte.
> Is uninitialized csect/rsect storage still an issue we should be concerned
> about?
>
Lest that be a concern, I'll update my earlier suggestion:
How about:
DC AL1(0) Allow at least one byte
DC 0H'0' Pad to even boundary; does nothing if already there.
ORG *-1 Back up to odd boundary.
OK. I'm an old timer; I didn't know about newer format of ORG.
Fewer mental gyrations for the reader than modulo arithmetic,
and no slack bytes. Does it generate too many TXT records?
I believe at most one.
Is PRINT GEN a concern? If the one-byte count is a constant,
could it be preset in both DC instructions?
Simpler is better. Lately a colleague, I consider her one of the
brightest, declined to use the limit argument of USING; future
shock. She added a CSECT boundary instead.
-- gil
