×
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.
hi David,
If the prototype specifies 5 parms, and 6 parms are specified on the
invocation ... the compiler will complain.
That assumes that there's only one prototype for a routine, and that
every program is using that prototype. I don't consider that a valid
assumption.
For example, what if someone comes along and decides to call your
subprocedure from CL (with CALLPRC). They can't use your existing
prototype, since CL doesn't understand RPG prototypes. There will be no
compiler error in that case.
Same is true of calling the routine from Cobol, C or C++. Or even SQL
or Java...
I agree that Dennis's technique is overkill in many cases. Like David,
I don't typically write code like his to check if the number of
parameters is valid unless I also have optional parameters. After all,
the caller will test his code, right? (right??) But I certainly see
where Dennis is coming from. It's a valid technique.
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.
midrange.com
