Re: Constants in Procedures

Kurt Anderson wrote:
> 
> Defining a constant in a subprocedure doesn't create any kind of
> run-time overhead since constants are 'evaluated' at compile-time,
> right?

Right.

> 
> I'd like to put a constant in a subprocedure because it will only be
> used in that subprocedure, although this particular procedure is going
> to be called over and over.
> 

That's a good idea to define the constant in the subprocedure if it is
only meaningful for the subprocedure.  Where you define the constant
won't make any difference at all to the runtime performance.  From a
runtime performance perspective, using a named constant is exactly the
same as using the actual literal.  The _name_ of the constant is only
used at compile time.