Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!ncar!gatech!udel!haven!ni.umd.edu!uc780.umd.edu!cs450a03
From: cs450a03@uc780.umd.edu
Newsgroups: comp.lang.misc
Subject: RE: CHALLENGE: typing and reusability
Message-ID: <8APR91.22400472@uc780.umd.edu>
Date: 8 Apr 91 22:40:04 GMT
References: <1404@optima.cs.arizona.edu> <27FA22CE.51A4@tct.com> <5APR91.00271522@uc780.umd.edu> <2800BB03.1D10@tct.com>
Sender: usenet@ni.umd.edu (USENET News System)
Organization: The University of Maryland University College
Lines: 20
Nntp-Posting-Host: uc780.umd.edu

Chip Salzenburg   >>>   or  >
Me                >>

>>> I like type safety.
>>(1) What is "type safety"?

>For me, it means that "messageNotUnderstood" is impossible unless I
>lie to the compiler.

Hmm...  Here's what I think you're saying:

messageNotUnderstood ---> run time error
lie to the compiler  ---> program bug

>>(3) How does that exclude dynamic typing?
>Dynamic typing permits "messageNotUnderstood".

not if you don't lie to the compiler

Raul Rockwell