|
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
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.