Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!batcomputer!cornell!rochester!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: <5APR91.00271522@uc780.umd.edu>
Date: 5 Apr 91 00:27:15 GMT
References: <1404@optima.cs.arizona.edu> <27FA22CE.51A4@tct.com>
Sender: usenet@ni.umd.edu (USENET News System)
Organization: The University of Maryland University College
Lines: 18
Nntp-Posting-Host: uc780.umd.edu

David Gudeman:
>>The problem with this and all the other solutions is that they
>>involve a non-trivial amount of extra work -- work that is only
>>necessary to overcome problems that are caused by static typing.
>>Rather than try to find ways around the problem, why not eliminate
>>the source of the problem?

Chip Salzenburg:
>Because I like type safety.
> 
>Next question?

Me (Raul Rockwell):
(1) What is "type safety"?

(2) How do you achieve it by static analysis of a program?

(3) How does that exclude dynamic typing?