Nested Calls

[Richard Kreiss]

Chain - replaces the current processing table with the one "chained to".  The chained processing executes from the top (first line).

Call - acts like a sub routine and runs until it reaches and end statement and returns to the point where the call took place.

I have a program which enters new unit owners and/or residents.  The first small processing table asks if this is a new owner or resident,.  based on the answer, the program chains to the proper processing table.  The owner processing table will delete all of the records relating to the previous owner.  The resident program does not do that nor does it need to get all of the information pertaining to the new owner or co-owner.

I have a library file of program snippets which I call as necessary.  This avoids repeating the same code over and over again.





> -----Original Message-----
> From: Filepro-list [mailto:filepro-list-
> bounces+rkreiss=verizon.net at lists.celestial.com] On Behalf Of Fairlight via
> Filepro-list
> Sent: Wednesday, May 2, 2018 7:13 PM
> To: filepro-list at lists.celestial.com
> Subject: Re: Nested Calls
> 
> On Wed, May 02, 2018 at 06:43:43PM -0400, Jose Lerebours via Filepro-list thus
> spoke:
> > On 05/02/2018 10:21 AM, Scott Walker via Filepro-list wrote:
> > >It makes it handy for programming with little chunks of reusable code that do
> not have to actually be copied to many different prc tables.
> > Kind of using UDFs (User Defined Functions).
> >
> > I have always used "chain" and/or "call" but more based on variable
> > setting (value) or conditional.  Personally, I rather return control
> > to "input", check on variable and call whatever needs to be called in
> > lieu of "nesting".
> 
> You're making routines which can be called from -anywhere-, regardless of
> surrounding flow, how?
> 
> CHAIN has always seemed like a bad/fragile idea to me, given how easy it is to
> misalign pointers.  Moreover, it's likely not meant to be used the same way CALL
> is used.  If I extrapolate correctly from the presence of both, CHAIN was -
> probably- meant to get around memory limitations in the old days, so you could
> have more code than could be resident at once.
> 
> I'm pretty sure they're meant for different tasks, and one is being abused.
> 
> m->
> --
> Audio panton, cogito singularis.
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 13889 bytes
Desc: not available
URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20180502/426a262b/attachment.bin>