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

Re: passing parameters longer than expected

Hi Dave

Is the prototype also using *VARSIZE? That will definitely remove the protection - with that, you are responsible for ensuring that the length is correct.

On 3/23/2012 6:22 AM, Dave wrote:
Hi, all,
I think this subject has been well debated in the past, but I just got
bitten again and would like to know how to protect myself in the
future. I copied and adapted some code and did not realise until well
into testing that I was passing a 100A parameter to a procedure
expecting 45A. I believe that when CONST is specified, the compiler
converts the parameter and there is no warning. I'm still wondering
why as I think that prototyping was introduced in order to protect one
against this sort of error. Now I discover that many other procedures
are doing the same call and I have to analyze to see if I can just go
ahead and change the 45A parameter to 100A

As an Amazon Associate we earn from qualifying purchases.

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