× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. March 2011

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



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.