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



I don't see where your prototype is defined in the sample code just in
Procedure interface. Maybe something is wrong there and being hidden by
CONST.



From:
Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
To:
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
Date:
02/18/2011 04:16 PM
Subject:
Re: Wanna see something scary?
Sent by:
rpg400-l-bounces@xxxxxxxxxxxx



MyParm is blanks inside of MyProc. Thus, tempvar gets set to blanks.
As a secondary issue, in debug, EVAL MYCONSTANT always returns
Identifier does not exist. I sort of expect that; constants don't tend
to show up in the debugger.

Joe
Do you see *blanks in temvar before the assignment of MyParm, after the
assignment of MyParm, or both before and after?



----- Original Message ----
From: Joe Pluta<joepluta@xxxxxxxxxxxxxxxxx>
To: RPG programming on the AS400 / iSeries<rpg400-l@xxxxxxxxxxxx>
Sent: Fri, February 18, 2011 1:22:45 PM
Subject: Wanna see something scary?

Take a look at this code:

d MyConstant c 'Data'

/free

DoProc();
*inlr = *on;

/end-free

p DoProc b
d pi
/free
MyProc( MyConstant);
/end-free
p e


p MyProc b
d pi
d MyParm 10 const
d tempvar s 10
/free
tempvar = MyParm;
/end-free
p e

What would you expect tempvar to get set to? I think it would be "Data"
but I would be wrong. It gets blanks, at least on my system.

Joe


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.