Rather than a trap representation I'd like a real trap, i.e. exception at runtime that can be caugth. Propagated NULL is useful in SQL but likely much less for

Rather than a trap representation I'd like a real trap, i.e. exception at runtime that can be caugth. Propagated NULL is useful in SQL but likely much less for integers as they are used as indexes. It is difficult to say when the "NaN" should result in a trap when doing pointer arithmetic using such numbers as the CPU does not have seperate pointer/integer data types. There are so many security problems from integer overflow. Also some easy way of checking an integer is in the range [0...n[ as a single instruction that traps if it is not.