RE: Using *OMIT & *NOPASS

[Phil Groschwitz <sublime78ska@xxxxxxxxx>]

> >
> > Proc X (a, b *nopass, c *nopass)
> >

I think if you use *nopass, you can't pass anymore
arguments (beyond the first *nopass).  For that you've
got to use *omit.

Phil

--- Scott Mildenberger <Smildenber@Washcorp.com>
wrote:
> I think you will have to use %parms to tell how many
> parms you received, I
> usually use a select statement when there are
> multiple possibilities.  One
> possibility would be if you can default the parms
> for the second call, you
> would still have to use %parms to determine whether
> the default was needed
> but you would only have to code the call's
> themselves in one spot.  It would
> be handy at times to be able to code the procedure
> interface so that a
> default is used for a parm if it isn't passed by the
> caller.
>
> Scott Mildenberger
>
> > -----Original Message-----
> > From: David Gibbs [mailto:dgibbs@mks.com]
> > Sent: Wednesday, November 28, 2001 8:57 AM
> > To: 'RPG400 Mailing List'
> > Subject: Using *OMIT & *NOPASS
> >
> >
> > Folks:
> >
> > I've got a bit of a quandary... We've been writing
> a number
> > procedures that
> > have a variable number of parameters.
> >
> > These procedures, in turn, call other procedures
> that also
> > have a variable
> > number of parameters.  The two procedures have
> very similar (if not
> > identical) parameter lists ... but the called
> parameter might call a
> > different procedure based on a control file.
> >
> > I made the erroneous conclusion that if a
> parameter was not
> > passed, it's
> > address would be set to *NULL (similar to passing
> *OMIT).
> >
> > So, the question is ... what is the best way to
> handle
> > possibility unpassed
> > parameters without having to code a complex
> structure of "if
> > %parms > 2,
> > call w/ 3 params, if %parms > 3, call w/ 4
> params", etc?
> >
> > Here's a quick pseudocode of what we are doing...
> >
> > Program Z
> >
> > callp x(a,b)
> >
> > end pgm z
> >
> > Proc X (a, b *nopass, c *nopass)
> >
> > if control file say one thing
> >     return Y (a,b,c)
> > else
> >     return W (a,b,c)
> > endif
> >
> > end proc X
> >
> > Proc Y (a, b *nopass, c *nopass)
> >
> > do stuff
> >
> > end proc Y
> >
> > Proc W (a, b *nopass, c *nopass)
> >
> > do other stuff
> >
> > end proc Y
> >
> >
> > david
> >
> > --
> > David Gibbs
> > Sr. Software Engineer
> > MKS, Inc.
> > 2500 S. Highland Ave, Suite 200
> > Lombard, IL  60148
> > (630) 495-2108 x5004
> >
> > Need a laugh (we all do these days): visit
> http://www.userfriendly.org
> >
> _______________________________________________
> This is the RPG programming on the AS400 / iSeries
> (RPG400-L) mailing list
> To post a message email: RPG400-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit:
> http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
> or email: RPG400-L-request@midrange.com
> Before posting, please take a moment to review the
> archives
> at http://archive.midrange.com/rpg400-l.
>


__________________________________________________
Do You Yahoo!?
Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1