Nested Calls

[Fairlight]

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.