Re: Allocation of local constant arrays

["Steve" <nospam_steved94@comcast.net>]

My opinion:
  It depends on the constants.

  If the constants are configuration values that someone might need to
change during maintenance, I tend to locate these values in an area near the
beginning of the package along with an explanation of their use.  This makes
it convenient for the maintainer.

  If the constants never change and are only relevent to the local function
or procedure, I tend to locate these values within the function or
procedure.

Steve
(The Duck)

"Davide" <ppp@ppp.it> wrote in message
news:c8hvcl$eth$1@e3k.asi.ansaldo.it...
>
> "Robert I. Eachus" <rieachus@comcast.net> ha scritto:
>
> > then put everything as constants in the
> > package body.
>
> As a general way to design the software, if you have constants used only
by
> a procedure, do you prefer (for the final application) to nest them in
that
> procedure or to keep them together with all the other constants in the
> package body, then visible also to procedures not referencing them?
>
> The question, in other words,  is: locate the data closest as possible to
> operations who used them or tend to "globalize" their visibility also when
> not necessary?
>
> Waiting for opinions.
>
> Davide.
>
>