Re: Does a null pointer always raise Constraint_Error?

[Florian Weimer <fw@deneb.enyo.de>]

Robert Dewar <robert_dewar@my-deja.com> writes:

> > There a two language-defined checks involved prior
> > to the array comparison.  However, 11.6(5) seems to
> > permit the omission of these checks, but I'm not
> > sure about that.
> 
> Nobody is sure about 11.6 :-)

:-)

> I don't think it applies however. Why not? Because
> the program does indeed depend on the result of this
> comparison. If you did
> 
>   Junk := a.all = b.all;
> 
> and never referenced junk, then you could use
> 11.6(5) to argue that the check should be omitted.

That's one of the simple cases everybody seems to be happy with.

I would argue that a.all and b.all are undefined, but because of their
type, their values can be compared with a well-defined result anyway.