Re: Explanation

On 2012-06-18, at 1:00 PM, rpg400-l-request@xxxxxxxxxxxx wrote:

What would be the benefit of your 'true' CONST over VALUE - performance
only?

Not really performance since a copy is being made both ways - VALUE or "real" CONST. But see below.

I guess I can see your point, but (and here I'm, only talking about parms
where the parameter doesn't need to be transformed) except for the
discussed scenario where the called program doesn't specify CONST, there
are very few occasions where a CONST parameter can be changed by the called
procedure anyway. How often do you run into those scenarios?

The major issue arises every time you call another language. Call CL(LE) and it can't use protos, call RPG III, call ... you get the picture.

By adding this option you would guarantee that the callers data cannot be messed up under any circumstances. It is one of the few omissions in RPG IV CALLP that can be better served by CALL/PARM with the old Factor1 and Factor2 options.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com