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



Don't quite understand this...

In my experience, signature management is easy. You simply use binder
source and a manually specified signature. The signature only needs to
change when a code change is not backwards compatible and the user must
recompile.

New procs are added to the end of the existing binder source.

New parms on an existing proc aren't an issue as long as you add them at
the end and make them *NOPASS.

I can go from a SRVPGM with
MyProc(parm1);

To
MyProc(parm1:parm2);
MyProc2(parm1);

without needing to recompile any code using MyProc(parm1);

Charles

On Wed, Jan 7, 2015 at 4:01 PM, Bradley Stone <bvstone@xxxxxxxxx> wrote:

The reason being is keeping track of signatures can get to be a nightmare.

For example, lets say you want to add a new settable variable.

Instead of adding a new subprocedure for that variable (or having to update
the current one and adding a new parameter to an already existant proc),
just add a new settable field in the setValue() proc. No new signature,
just an updated version.


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.