Run-time Checks for C

[Jin Li]

In article <10113 at umn-cs.CS.UMN.EDU> raghavan at umn-cs.cs.umn.edu (Vijay Raghavan) writes:
>...
>the C language definition doesn't really preclude any implementation from
>doing certain run-time checks (for array bounds, type checking, referring
>contents of uninitialized pointer variables &c), it's just that most
>(okay, all!) implementations don't do any such checking because of efficiency
>reasons. Now I'm not sure that this statement is really true (I mean I'm not
>sure that sufficient information can always be passed to the compiler for it
>to generate code for meaningful run-time checks.) ...

There are C compiler/interpreter which do run-time checks, but the cost
is too high.  However, do you really want to ride on a $$$$$.$$
tricycle when you can ride on a $ mountain bike?

-- 
		Jin Li			     >>    Gin & Tonic mix well.
University of Toronto Computing Services    << 
jinli at gpu.utcs.utoronto.ca  uunet!utgpu!jinli>>