RE: Externalize DB/IO (was What Counts as Technically Slick?)

Looks like murky semantic waters to me.  Since the default parameter passing
method is by reference, the pointer may or may not be necessary.  In either
case you need to know the file layout at some point so you can do things
with the fields.

> -----Original Message-----
> From: Nathan M. Andelin [mailto:nathanma@haaga.com]
> Sent: Wednesday, April 11, 2001 7:38 AM
> To: MIDRANGE-L@midrange.com
> Subject: RE: Externalize DB/IO (was What Counts as Technically Slick?)
> 
> 
> >From: "Stone, Brad V (TC)" <bvstone@taylorcorp.com>
> 
> >I agree with John.  The biggest problem that I've run into is
> >changing parm lists for subprocedures.  Now, after getting
> >into Java and OO, this makes more sense to do, and I'm not
> >sure why I didn't do it in the first place. It does make sense.
> >I'd option to simply pass a pointer to a DS as the only
> >parm.
> 
> Syntax # 1:
> 
> D myStructure E DS ExtName(myFile) Import
> 
> C Eval myReturn = myFunction()
> 
> Syntax # 2:
> 
> D myStructure E DS ExtName(myFile) Based(myBasePointer)
> 
> C Eval myReturn = myFunction(myBasePointer)
> 
> I'm trying to determine whether Syntax # 2 is better than 
> Syntax # 1.  They
> are functionally equivalent.  Under Syntax # 2, myFunction 
> must explicitly
> set myBasePointer to the address of it's version of 
> myStructure.  Under
> Syntax # 1, the pointer mapping is implied.
> 
> Any suggestions?  Thanks.
> 
> Nathan.
> 
> 
+---
| 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
+---