RE: Calling similiar (overloaded) procedure that has *nopass *omit inthe parameter

At last year's WMCPA conference I was told that RPG procedure overloading was in the works. Or on the list. At the very least it has been talked about. Would love to see it come down the line.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of hockchai Lim
Sent: Tuesday, March 08, 2011 1:16 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Calling similiar (overloaded) procedure that has *nopass *omit inthe parameter

sigh... I looks really ugly when there are 16 *nopass parameter involved....

Kind of wish Barbara can do something about this.......heehee

"Charles Wilt" <charles.wilt@xxxxxxxxx> wrote in message news:mailman.32973.1299611621.2702.rpg400-l@xxxxxxxxxxxx...
Well not quite as bad as I thought...at least you can pass the omitted parm through without having to check it

select;
when %parms() = 3;
Proc2(parm1:parm2:parm3);
when %parms() = 2;
Proc2(parm1:parm2);
other;
Proc2(parm1);
endsl;

Note the above uses a 10a CONST parm1 for ease of testing...your procedure will be more complex.

You could also simplify procedure handling in Proc2, remove the *NOPASS and code the above as

select;
when %parms() = 3;
Proc2(parm1:parm2:parm3);
when %parms() = 2;
Proc2(parm1:parm2:*OMIT);
other;
Proc2(parm1:*OMIT:*OMIT);
endsl;
HTH,
Charles

On Tue, Mar 8, 2011 at 1:51 PM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:

There isn't an easy way...since RPG doesn't offer true null support...

Proc1 will be (big) select statement that determines which way to call
Proc2...

Parm1 is also going to be problamatic since it's not defined CONST or
VALUE...are you really using it for output?

Charles

On Tue, Mar 8, 2011 at 11:44 AM, hockchai Lim
<lim.hock-chai@xxxxxxxxxxxxxxx> wrote:

Assuming that proc1 is an overloaded procedure of proc2. Proc1
contains no business logic. All it does is converting the parm1 into
alpha and calls proc2. As you can see, both parameter 2 & 3 in proc1
& proc2 are *nopass and *omit type parameters. Can someone give me a
pointer on best approach on calling proc2 from proc1?



D proc1 pr
D parm1 10p 0
D parm2 10 options(*nopass :*omit) const D parm3 10 options(*nopass
:*omit) const

D proc2 pr
D parm1 10
D parm2 10 options(*nopass :*omit) const D parm3 10 options(*nopass
:*omit) const


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

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