Darren New wrote:
> Chris Smith wrote:
>> Specialized
>> language already exist that reliably (as in, all the time) move array
>> bounds checking to compile time;
>
> It sounds like this means the programmer has to code up what it means to
> index off an array, yes? Otherwise, I can't imagine how
George Neuner wrote:
> The point is really that the checks that prevent these things
[such as 'array index out of bounds']
> must be
> performed at runtime and can't be prevented by any practical type
> analysis performed at compile time. I'm not a type theorist but my
> opinion is that a stati
Pascal Costanza wrote:
> There is, of course, room for research on performing static type checks
> in a running system, for example immediately after or before a software
> update is applied, or maybe even on separate type checking on software
> increments such that guarantees for their composition
