RE: Basing Pointers

[Colin Williams <Williamsc@xxxxxxxxxxxxxxxxx>]

Ok, another idea, how about letting you declare the basing pointer
outside of the DS, so allowing you to redefine the 
data structure as BASED eg:

/COPY contains:
DSAPIdatastructure
        Subfield1       1 2
        Subfield2       3 4     

then within the main source member:

DSAPIdatastructure              BASED(Ptr1)

This would still be at compile time, but would mean that you would not
have to make any changes to your /COPY

-----Original Message-----
From: Jon.Paris@halinfo.it [mailto:Jon.Paris@halinfo.it]
Sent: Wednesday, May 19, 1999 4:45 AM
To: MIDRANGE-L@midrange.com
Subject: Basing Pointers




 >> Another alternative may be to define the DS both ways and use some
like /IF
DEFINED(USEBASED)... /ELSE... ENDIF.  This would not affect existing
code, and
the documentation would not need a lot of changing.

Good idea David - I agree that for multi-DS members they can't just
leave off
the first line.  The reason I didn't suggest conditional compilation
directives
is I'm not sure how many releases back they expect the includes to cover
and it
was only introduced in V3R7.


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---