RE: Grrr... signature violation

[Scott Mildenberger <Smildenber@xxxxxxxxxxxx>]

You can add a parameter to a procedure and it does not change the signature
of the service program.  You will not need to set up a new version in the
binder source.  Programs will not get a signature violation, they will get
an error if the parameter is not set up to be optional.  Any programs that
need to use the new parameter will have to be recompiled (edited for that
matter to add the parm).

Scott Mildenberger

> -----Original Message-----
> From: Bartell, Aaron L. (TC) [mailto:ALBartell@taylorcorp.com]
> Sent: Friday, May 03, 2002 1:06 PM
> To: 'rpg400-l@midrange.com'
> Subject: RE: Grrr... signature violation
>
>
> <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.
>
> Aaron Bartell
>