Re: To Initialise or not

[dewar@cs.nyu.edu (Robert Dewar)]

T.E.D. said

"Yes, but I don't think any compiler COULD easily help enforce this (It
sounds a lot like the halting problem to me). That is what code
walkthroughs are for."

(speaking of the idea of considering it to be "wrong" to reference a
default initialized access value.

Help means help. It does not mean solving the halting problem. It is
perfectly fine and easy for a compiler to give warnings in simple
cases (it is no different from giving these warnings for the cases
of other datatypes, such as integer). You can do it some of the time,
and that is helpful.

For example:

procedure q is
  type x is access integer;
  y : x;
  z : x;
begin
   z := y;
end;

This could certainly give a diagnostic if the appropriate option is set.

I almost wondered if it should give a diagnostic ("y is never assigned
a value") warning unconditionally. One version of GNAT did so, then we
took it out.

This is yet another case where I miss the capability of having a default
initialized constant. Yes in this case we could say

  y : constant x := null;

but in the record case, there is no easy way of doing this.