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

Re: Optional parameters

On 12/16/2009 12:19 PM, Scott Klement wrote:
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.

Good point.

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.

I would agree it's a valid technique ... but if you're worried about the consumer of your procedure passing an invalid number of parameters, then I would say it's more of a risk that they pass in totally invalid parameters.

In the end (IMO), if you're worried about the procedure being called with the wrong number of parameters ... you have bigger problems to deal with.

david


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.