Why type checking is done at compile time

Thread View: comp.lang.functional

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by morrison Fri, 03 Aug 1990 14:43

#414

Author: morrison
Date: Fri, 03 Aug 1990 14:43

26 lines
1431 bytes

Hello,

The question has been raised on why type checking is always
done at compile time (even conceptually).  I believe this 
question deserves a simple answer (and it is NOT because of
efficiency).

A type system is basically a very simple and specialized 
type of program verifyer.  If the type system is 'type-safe'
(a VERY desirable property of a type system) and a program
passes the type checker, then the programmer is GUARENTEED 
that there will be no type conflicts at run time.  

Run time type checking does NOT do this.  It simply allows the
programmer to do something 'exceptional' when such a 'error'
occurs.   Run as many test cases on the code as you like, you
will never get the guarentee of type safety that the compile
time type system gives you.

Thus a type system is simply the first modest step in program
verification (that is determining run time behavior by analysing
the program text).   

Vance Morrison
Univ of Il.

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads