Re: AW: More on RPG style

Huh, that's weird, I thought it worked fine as-is. Maybe it's a V5R4 thing
(I compiled at V5R4, I think).

Yeah, the _NPMPARMLISTADDR thing *is* cool, isn't it? I found it a couple of
years ago and played with it for exactly this reason (where I have multiple
'duplicate' parameters). Note that with parameters passed by value, it gets
significantly more complex....

On Sat, Mar 6, 2010 at 4:15 AM, Dennis Lovelady <iseries@xxxxxxxxxxxx>wrote:

OK, so here it is. I *could* have gone with the simple routine for the
in_int() procedure (just comparing passed parameters, as with the basic
character version), but I figured "why not make it complicated"! So I

Rory, there are three things here that spark my interest. First is the @in
capability itself, which is way-cool-looking. Second is the
_NPMPARMLISTADDR procedure, which I wasn't aware of before, but I hope to
exploit in another variable-parms situation I've been toying with. Finally
is the overloading, and it is here that I had difficulty. (Solved now.)

When I try to compile it as-is on V5R3, I receive CPD5D02 "Definition not
found for symbol '@in'"

I presume this has to do with the double prototype definition of procedure
@in (@in2). I broke the program into two pieces: IN_SET and @IN (where @IN
is the module that does all the work; IN_SET is just the main). This makes
sense anyway since this makes the most sense as a module in a service
program. But --- no joy. I still got CPD5D02 (referencing @in) on the
CRTPGM command: CRTPGM PGM(IN_SET) MODULE(IN_SET @IN)

I was able to resolve this by putting Export on the P-specification for the
@IN procedure. Thought you should know. I don't know if that would have
helped with the program as a self-supporting entity.

Now I'm off to study that cool _NPMPARMLISTADDR proc. Thanks so much!

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Abstract Art: A product of the untalented, sold by the unprincipled to the
utterly bewildered."
-- Al Capp