× 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. MIDRANGE-L
  3. March 2009

Re: Odd CALLPRC behavior when using RPG indicator with RTNVAL

On Thu, Mar 12, 2009 at 5:00 PM, Scott Klement
<midrange-l@xxxxxxxxxxxxxxxx> wrote:
Charles Wilt wrote:
In both cases, the code that breaks wasn't "correct" in the first
place.  In may have worked, but that was basically luck.

What wasn't correct to begin with was the fact the CL and RPG weren't
compatible!  If they wanted to fix something, they should've fixed THAT
and eliminated the need for the ExtProc(*CL) kludge.

Interesting point Scott, but I assume IBM had reasons for it. Does
anybody (Jon, Barbara) know why? Perhaps fixing it "properly" would
have broken more code?

Charles Wilt

As an Amazon Associate we earn from qualifying purchases.

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

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