• Subject: Re: MIDRANGE-L Digest V4 #363
  • From: Jim Langston <jimlangston@xxxxxxxxxxxxxxxx>
  • Date: Wed, 11 Apr 2001 11:29:41 -0700
  • Organization: Pacer International

Well, syntax # 1 is much easier for me to read and understand in a program.
Syntax # 2 makes me scratch my head and wonder what is going on.

I have always been one to put complexity into the called procedure rather
than the calling procedure.  The reason being any fixes/modifications would
only have to be done in the called procedure once, and also, once the called
procedure is done they are usually not touched again for a long period of time.

So, I would go with Syntax # 1 definitely.

Regards,

Jim Langston

Date: Wed, 11 Apr 2001 08:38:01 -0600
From: "Nathan M. Andelin" <nathanma@haaga.com>
Subject: RE: Externalize DB/IO (was What Counts as Technically Slick?)

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
+---

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].