Constant as anonymous functions : the outer space beast is back

["Hibou57 (Yannick Duchêne)" <yannick_duchene@yahoo.fr>]

Hi,

I'm back with the topic “ constant as anonymous functions ” ( I've
opened last year, about 10 months ago if my mind is right ) with a new
argument advocating for it : I have a simple design rule which state
that I automatically add a “ pragma Elaborate_Body ” in the heading of
a package specification, as soon as this package defines functions
which have the semantic of constants, because dependencies to the
specifications as supposed to be possible dependencies to these “
constants ”, and as elaboration of these “ constants ” requires body
elaboration, a dependency to such a package specification is supposed
to probably requires body elaboration.

Here we are : the lack of constants as anonymous functions turn into
consequences on the package elaboration order. That's big (at least to
me).

Another argument : enabling constants to be anonymous functions would
allow to change a functions into a constant without breaking anything,
unlike what is in the actual state. Actually, there seems to be a kind
of implementation dependency in specifications due to the lack of
constants as functions.

Third, but already pointed (as I remember) when the topic was opened
about ten months ago : this would not break any existing sources and
designs.

Who want to talk about this subject ?