|
On Fri, 3 May 2002, Bartell, Aaron L. (TC) wrote: > > <snip> > No. Changing the parameters will not change the signature, unless you > also change the name of the procedure, or change the order, etc. > </snip> > > That's what I said in more words or less. If you change the parameters, so > let's say I added one onto the end of a sub procedure, you indirectly change > the signature because you will now have to create a new version in the > binder language or recompile all of the programs that were previously > compiled to the old parameter list to now look at the new parm list. Or am > I still off. I can't see a difference in what I said compared to what you > said, Scott. The reason that I don't think you're saying the same thing is that you say things like this: "If you change the parameters, so let's say that I added one onto the end of a sub procedure, you indirectly change the signature..." No. Adding a parameter does not change the signature. You don't have to change the binding language, because parameters aren't in the binding language. You don't have to recompile anything but the service program. If you have this procedure: P beat_horse B EXPORT D beat_horse PI D horse_ptr * value D stick_type 1A const And you add a parameter to it: P beat_horse B EXPORT D beat_horse PI D horse_ptr * value D stick_type 1A const D num_times 10I 0 value options(*nopass) This does NOT affect the signature. You only have to recompile the service program. The other programs work fine. There's nothing to change in the binding language, because binding language doesn't deal with paramters -- it deals with EXPORTS. However, you seem to be saying that you're doing THIS instead: P beat_horse B EXPORT D beat_horse PI D horse_ptr * value D stick_type 1A const P beat_horse2 B EXPORT D beat_horse2 PI D horse_ptr * value D stick_type 1A const D num_times 10I 0 value This *WOULD* change the signature, because you're adding a new export called "beat_horse2". Which would then have to be added to the binding source. Sorry for the procedure names :)
As an Amazon Associate we earn from qualifying purchases.
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.