× 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.



We do use the binder language and keep a consistent (hardcoded) signature. Putting this on my to-do list for Wed, thanks.

-Kurt

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Tuesday, October 11, 2011 3:46 PM
To: RPG programming on the IBM i / System i
Subject: Re: 1 byte return parameter to CL

Hi Kurt,

This change is no different from changing a parameter on a prototype.

Whether you need to re-bind all callers that use that service program depends on your shop's signature strategy. Do you use binder language to keep a consistent signature between service program updates? Or how do you control your signature?

If you keep a consistent signature, then yes, you only need to recompile (both recompile and re-bind) the callers of that specific procedure.

If you do not keep a consistent signature, then you need to recompile all callers of that procedure, but you'll have to re-bind everything.


On 10/11/2011 3:05 PM, Kurt Anderson wrote:
Thanks for the detailed response.

So I'm clear, if I change the prototype to use ExtProc, I only need
to recompile any programs that use that specific procedure, correct?
Or do I need to recompile all programs that use the service program?
If the former is true, I think making the change is reasonable, if
not, I'll likely write a wrapper procedure as you suggest.


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.