Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!decwrl!deccrl!bloom-beacon!eru!hagbard!sunic!mcsun!ukc!edcastle!cs.ed.ac.uk!cs.edinburgh.ac.uk!nick
From: nick@cs.edinburgh.ac.uk (Nick Rothwell)
Newsgroups: comp.lang.misc
Subject: RE: Dynamic typing (part 31,497)
Message-ID: <8872@skye.cs.ed.ac.uk>
Date: 15 Apr 91 12:11:19 GMT
References: <1707@optima.cs.arizona.edu> <8742@skye.cs.ed.ac.uk> <11APR91.19025118@uc780.umd.edu>
Sender: nnews@cs.ed.ac.uk
Reply-To: nick@lfcs.ed.ac.uk
Organization: Tasha Yar Appreciation Soc... oh, sh*t
Lines: 20

In article <11APR91.19025118@uc780.umd.edu>, cs450a03@uc780.umd.edu writes:
> Nick Rothwell writes:
> >Fair enough. I choose the benefits of static typing (no runtime errors,
>                                                       ^^^^^^^^^^^^^^^^^
> Seriously?  How is this accomplished?

Oh nuts, my fault for being too hasty.

No runtime *type* errors. Runtime errors are restricted to a small set of
exception conditions defined by the language. These can be caught and
handled, and the exception mechanism allows you to define you own exception
values and raise and handle them. I'm talking about ML here, btw.

	Nick.

-- 
Nick Rothwell,	Laboratory for Foundations of Computer Science, Edinburgh.
                nick@lfcs.ed.ac.uk    <Atlantic Ocean>!mcsun!ukc!lfcs!nick
~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~
           "I see what you see: Nurse Bibs on a rubber horse."