language problem

[drw@cullvax.UUCP]

keith@telesoft.UUCP (Keith Shillington @prodigal) writes:
> Dale Worley at Cullinet Software writes:
> > Is the following program required to raise CONSTRAINT_ERROR (or whatever)?
> > 
> > procedure y is
> >   subtype x is range 0..100;
> >   a : x := 100;
> > begin
> >   a := a + 1;
> > end y;
> > 
> [keith replaces "subtype" with "type" so the code will compile.]
> 
> So, making that suggested modification results in correct compilation
> with the runtime result:
> 
> >>> Unhandled exception: CONSTRAINT_ERROR  (Range Check)
>     Raised in   Y.Y at line 5
> 
> So, yes, absolutely, constraint_error should be raised. [...]

But I am neither asking whether you thing that it should be raised,
nor whether your favorite implementation raises it, I am asking
whether the LRM *requires* that it be raised, or is an implementation
allowed to not raise it?

Sheesh!  Don't people understand what *standards* are?

Dale
-- 
Dale Worley		Cullinet Software
UUCP: ...!seismo!harvard!mit-eddie!cullvax!drw
ARPA: cullvax!drw@eddie.mit.edu
Un*x (a generic name for a class of OS's) != Unix (AT&T's brand of such)