Re: Re[2]: Value vs. Const

["Joep Beckeringh" <joep.beckeringh@xxxxxxxxxx>]

Scott,

> The procedure still receives a
> read-only pointer to the data in question, rather than the value of the
> data.

I doubt whether that is completely accurate; I don't think it is a read-only
pointer, but just a pointer.

If I understand things correctly, the CONST in the prototype is just a
promise to the compiler that the called procedure or program won't change
whatever the pointer is pointing at (thereby making it possible for the
compiler to use a temporary variable). I use CONST often in prototypes for
API calls; where the only guarantee that the parameter won't be changed is
the documentation.

The CONST in the procedure interface is different, of course; the compiler
checks that the procedure doesn't change the parameter.

Joep Beckeringh