Re: OVERLOAD matching: varchar(10) & varchar(20)

Well - that might help now, but it might also cause problems in the future when compiling programs, that depend on the first (old) prototype.

With CONST one can code procedure(variable:...) or procedure('HELLO':...) - without CONST you can't supply the parameter as a literal.

So - what is the intention of having two procedures where one parameter is VARCHAR(20) or VARCHAR(10)? As you had CONST, it wasn't a "return-parameter".

HTH
Daniel

Am 02.02.2026 um 15:54 schrieb Justin Taylor <jtaylor.0ab@xxxxxxxxx>:

The parms did have CONST. I removed it, and now it works.

Thanks

On Mon, Feb 2, 2026 at 8:13 AM Daniel Gross <daniel@xxxxxxxx> wrote:

If both parameters are VARCHAR - they will probably both match - this
happens often when using CONST or VALUES.

The best way would be to post the prototypes here, so we can see what
happens, and what's possible or not.

HTH
Daniel

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.