What's "wrong" with it is that EQU * is merely a gratuitous way to hide
your intention on any alignment requirement.  Does EQU * give you any
advantage over DS    0X?

The statement earlier about "stick a pin right here" is just specious.  Is
there some confusion that regular DS/DC symbols might wander off somewhere?

Not that I want to come off snarky, but IBM provides plenty of poor coding
examples in various MACLIBs.  And, plenty of good ones too, but you have to
use some judgement.

sas

On Thu, Aug 2, 2018 at 12:02 PM, Phil Smith III <[email protected]> wrote:

> Steve Smith wrote, in part:
>
> >Note that I don't think EQU * should be used in data areas either, where
> it
>
> >is potentially more dangerous.   This is the kind of error that motivated
>
> >me to write this up.
>
>
>
> I'm sure it can be; what's wrong with this:
>
>
>
> SOME     DSECT ,
>
> SOMEA    DS    F
>
> SOMEB    DS    F
>
> SOMENAME DS    CL8
>
> SOMEREST EQU   *
>
>
>
> In this case, SOMEREST is the end of the defined part of the DSECT and the
> rest is some sort of free-fire zone (or mapped by other DSECTs, or
> whatever). I've done that a million times, never regretted it; IBM does it
> all the time. What's wrong with it?
>
>
>
> .phsiii (this is fun!)
>



-- 
sas

Reply via email to