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

Subject: Re: Odd CALLPRC behavior when using RPG indicator with RTNVAL
From: Barbara Morris <bmorris@xxxxxxxxxx>
Date: Fri, 13 Mar 2009 11:43:16 -0400
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>

Charles Wilt wrote:

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?

There was no way to fix it without breaking existing applications. If either RPG+COBOL or CL had changed how they handle 1 byte character/indicator return values, it would have required a recompile of all existing programs.

See my response (apology) on the RPG list: http://archive.midrange.com/rpg400-l/200903/msg00140.html

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

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

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.