Re: Odd CALLPRC behavior when using RPG indicator with RTNVAL -- MIDRANGE-L

Subject: Re: Odd CALLPRC behavior when using RPG indicator with RTNVAL
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Thu, 12 Mar 2009 14:19:38 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

David Gibbs wrote:

I'm not sure that's correct ... if the RPG procedure has
extproc(*cl:name) defined, I *THINK* that should allow the procedure
to be called from both RPG and CL, but it will use CL return
parameter mechanism.

At this point, my biggest gripe is the fact that I have to rework and retest code that's worked fine for years.

david

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Odd CALLPRC behavior when using RPG indicator with RTNVAL , rob

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.