× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. August 2009

Re: Guaranteeing re-resolution on CALL statements

Jon,

I would assume (and *there's* the problem) that you'd only do a
forced-re-resolve if you knew the program had been changed. Perhaps via a
flag (as you suggest).

Of couse, a wasted call is a fraction of a second, even including pointer
resolution.

Rory

On Wed, Aug 12, 2009 at 1:53 PM, Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:

Reading this gave me an idea. Rather than "wasting" a program call
each time to force the resolution why not have the "dummy" program
simply call the one you want and thewn have the logic flip-flop
between a direct call and an indirect via the dummy.

Not exactly intuitive - but then nothing is in this scenario!


Jon Paris


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.