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



This is a comment not specifically to Dave's post but also to the post he was commenting on.

Programs can ONLY receive parameters by reference. The VALUE keyword is not permitted on a PI/PR for a program. If a parm is declared as CONST then IF it does not match the definition a copy is made and a pointer to the copy is passed. In all other cases a pointer to the original data is passed.

For procedures parms can be passed by reference or value. In both cases the parameters are effectively pushed onto the stack and then popped in the called procedure. If you pass a field by value a copy of the actual data is pushed on the stack. There are minor exceptions to this in a few oddball cases such as floating point fields but it is valid to think it this way.



On Mar 11, 2020, at 5:02 PM, dlclark@xxxxxxxxxxxxxxxx wrote:

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 03/11/2020
04:38:34 PM:
In which case, the variabkle is copied to a new location and *pointer to

new location* is passed to procedure.

In the end, you always passed a pointer under covert....


I used to think that. But then I ran into the situation where one
program was passing a parameter by reference (by default) but the called
program expected the parameter to be passed by value (explicitly) and the
called program couldn't see the passed value at all. Explain to me why is
that? Thanks for the education.


Sincerely,

Dave Clark
--
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300

Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331




*********************************************************************************************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary
information. If you have received this message in error, please
immediately notify the sender and delete and destroy the message and all
copies. All unauthorized direct or indirect use or disclosure of this
message is strictly prohibited. No right to confidentiality or privilege
is waived or lost by any error in transmission.
*********************************************************************************************
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com


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.