Re: Value vs. Const

Joel Cochran wrote:
> 
> One caveat that Barbara Morris pointed out to me is that using "value"
> and "options(*nopass)" on the same variable can be dangerous.  If you
> want a variable to be *nopass and still take advantage of the VALUE
> benefits, then use CONST...
> 

Joel, just to clarify, it's ok to use VALUE and options(*nopass)
together as long as you make sure the parameter was passed before using
it.  But with CONST, you shouldn't refer to the parameter if it wasn't
passed, either.  So I don't think there's any reason not to use VALUE
and OPTIONS(*NOPASS).

(The dangerous thing you were doing was using the unpassed parameter as
though it was a local variable.)