× 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. April 2004

Re: Parameter passing RPV III <--> RPG IV vs. RPG IV <--> RPG IV

This is not the only situation where you would think something should have bombed and didn't.

More than once I have wracked my brain looking for a problem because something has the exact, precise same code as always and the last time it was changed was eight years ago, and yet some new data value or some new situation, or who knows what, was different today.

- Alan


Joep Beckeringh wrote:

Charles,

I think you were lucky that it worked. In the caller you have field P@ERR defined as 1 byte. When you call CADATE you are passing a pointer to this field. Now when CADATE puts '123' in the memory that the pointer points at, the '1' ends up in field P@ERR, but '23' ends up in whatever variable happens to sit next to P@ERR. It is quite possible that in the memory layout that the RPG III compiler generated this did no harm, while in the RPG IV layout it did.

Joep Beckeringh



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.