× 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.



You can specify a constant numeric value that represents the maximum
number of parameters your procedure can receive, then within the code,
check against that value, so when you have to maintain the procedure in
the future, you only need change the constant, not every instance you
check the number of parameters. 

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Sean@xxxxxxxxxx
Sent: Thursday, November 11, 2004 1:55 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Programmatically determine number of parms in procedure
prototype?

All,

When using OPTIONS(*NOPASS) in a procedure parameter definition, it is
necessary to use the BIF %PARMS to determine the number of parms that
were passed.

Is it possible to determine the maximum number of parameters for a
procedure prototype?  It would be great to be able to do something like:

IF %PARMS = <total number of parms> THEN ...

or

IF %PARMS = <total number of parms - x> THEN ...

At times, I have a parm at the bottom of the list that is optional;
adding more parms above it means that I need to go back through update
the code that uses that bottom-most parm.

Any thoughts?

Thanks,
-Sean

--
This is the RPG programming on the AS400 / iSeries (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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.