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

I know I'm lucky...well actually the original programmer was lucky since
1999 ;-)

As I discuss in my reply to Scott, apparently the '23' in the RPG III
version ended up someplace that caused the loop to end as it should have.
Thus it seemed as if the program was running correctly.

I wish I could find out just were it ended up.  Just because I'm curious as
to how exactly the loop ended.  I don't think the ended up in the variables
controlling the loop, but somewhere else instead.

Thanks the reply,
Charles


> -----Original Message-----
> From: Joep Beckeringh [mailto:joep@xxxxxxxxxxxxxxxxxxx]
> Sent: Wednesday, April 14, 2004 5:43 PM
> To: RPG programming on the AS400 / iSeries
> Subject: Re: Parameter passing RPV III <--> RPG IV vs. RPG IV 
> <--> RPG IV
> 
> 
> 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
> 
>