Re[2]: Value vs. Const

[Scott Klement <klemscot@xxxxxxxxxxxx>]

On Fri, 8 Aug 2003, Rick Rauterkus wrote:
>
> Ok, after re-reading this, a question comes to mind. If I specify the
> parameter as CONST, I can still call the procedure using a literal,
> expression, or a variable with a different length, correct?

Correct.

> Would it act like VALUE then, creating a copy in the called procedure's
> memory for its use?

Sort of.

If the data type does not match, or a calculation has to be done, etc.
Temporary memory is allocated, and the value is copied into it.   But,
this is done outside of the procedure.  The procedure still receives a
read-only pointer to the data in question, rather than the value of the
data.

Also, remember that you can change a parm passed by value in the
subprocedure (without affecting the caller's copy).   You cannot directly
change a CONST parameter, ever.

Hope that made sense...