Re: passing parameters longer than expected -- RPG400-L

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

I find I have the same question as Scott - what happened that bit you? What wrong result did you get? That was never clear in all of this thread.

One thing I can think of - the text of the 100A was truncated on a report - this would happen if the string were longer than 45 - is this the problem? I have seen this happen.

Regards
Vern

On 3/26/2012 6:25 AM, Dave wrote:

So I'm surprised by how you say this "bit you" and that you wish the
system would warn you? What problem does it cause?

Hi Scott,
I was using code that was already used and did not realize the error
before well into my tests. The same problem could be produced
elsewhere, as other developpers have copied this same error. There was
absolutely no reason to pass the parameters in this way. As we use
CONST on all input parameters, the situation that you describe is not
likely to happen, but if CONST were not used, I am also supprised that
there is no message from the compiler. I do not think that all in our
shop are aware of the result that would produce. It seems to me that
prototyping only offers an aid to compiling and not complete
protection from passing wrong parameters.

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.