Re: Value vs. Const

[rob@xxxxxxxxx]

Normally I use CONST.  However if you find that in the subprocedure that 
the first thing you are doing is copying the variable over to another one 
so that you may modify it, then I'd use VALUE.  I think we both understand 
that this modification is not passed back to the main program unless we 
omit both VALUE and CONST.

An example of 'maybe' a good use of VALUE:

/free
  parm=%abs(parm);
  return parm*25;
/end-free

But if you're doing:
/free
  WorkVar=%abs(parm);
  return parm*25;
/end-free

Then you could get by with CONST.  But then you have the overhead of 
another variable, etc.  And, of course I realize that you could do:
/free
  return %abs(parm)*25;
/end-free

just trying an example.


Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin