Xref: utzoo comp.lang.misc:7115 comp.object:2926 comp.lang.eiffel:1473
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uunet!igor!rutabaga!jls
From: jls@rutabaga.Rational.COM (Jim Showalter)
Newsgroups: comp.lang.misc,comp.object,comp.lang.eiffel
Subject: Re: CHALLENGE: typing and reusability (was: Re: blip)
Message-ID: <jls.670121104@rutabaga>
Date: 28 Mar 91 00:45:04 GMT
References: <jls.669591628@rutabaga> <1991Mar22.210725.29448@neon.Stanford.EDU> <1991Mar26.005805.1914@kodak.kodak.com> <1991Mar27.040253.17343@leland.Stanford.EDU>
Sender: news@Rational.COM
Followup-To: comp.lang.misc
Lines: 15

>Sure, type errors would result in a statically-typed language, and
>run-time errors in a dynamically-typed language.  There's no problem
>with that:

Uh, yes there is. The Achilles Heel of dynamically-typed languages is
run-time errors. These may be fine for WIMPS interfaces on workstations:
just print out "Window Manager is confused", abort, and let the user
reboot the system. ;-)

This gets a little trickier when the code is running embedded in a
$100 million satellite orbiting Venus.
--
***** DISCLAIMER: The opinions expressed herein are my own, except in
      the realm of software engineering, in which case I've borrowed
      them from incredibly smart people.