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

Optional Parameters in Subprocedures

 >> If you are using the %addr, then why bother with the %parms?

Because there is nothing to say that there is not a null pointer (or data
that will test as a null pointer) already on the stack just waiting for the
unwary!!  Even worse (and I've seen the really nasty effect of this one)
there may be a perfectly _valid_ pointer on the stack.  It wasn't passed and
has nothing to do with the current call but if data gets moved to that field
good luck in tracking down the error!!

You should only check the %addr of a parameter you _know_ to have been
passed - hence the use of %parms

Jon Paris
Partner400

As an Amazon Associate we earn from qualifying purchases.

This thread ...
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.