Re: Calling similiar (overloaded) procedure that has *nopass *omit in the parameter

I think you should strive to avoid using *OMIT and *NOPASS; do not
design or write any new code that requires their use (e.g. in your own
procedures); -- only use them when absolutely necessary (e.g. when
calling some IBM APIs or some other vendor code that requires this.)

That's my opinion, and I'm sticking to it. ;-)

HTH,

Mark S. Waterbury

 > On 3/8/2011 11:44 AM, hockchai Lim 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.