Newsgroups: comp.lang.misc
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!lavaca.uh.edu!menudo.uh.edu!sugar!ficc!peter
From: peter@ficc.ferranti.com (Peter da Silva)
Subject: Re: Dynamic typing (part 3)
Message-ID: <EACAIH5@xds13.ferranti.com>
Reply-To: peter@ficc.ferranti.com (Peter da Silva)
Organization: Xenix Support, FICC
References: <1211@optima.cs.arizona.edu> <3073:Mar2820:38:5191@kramden.acf.nyu.edu>
Date: Fri, 29 Mar 91 15:39:06 GMT

In article <3073:Mar2820:38:5191@kramden.acf.nyu.edu> brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:
> A good preprocessor will
> smooth out the differences either way; so, all else being equal, you
> might as well choose the model that produces better code, i.e., static
> typing (at least with current technology).

If raw execution speed is the most important criterion, this is true. But
then you should probably be coding in assembly. If coding speed is the most
important criterion, then you might as well use a dynamically typed language.

Use the right tool for the job. Your job, apparently, is pumping bits.
-- 
Peter da Silva.  `-_-'  peter@ferranti.com
+1 713 274 5180.  'U`  "Have you hugged your wolf today?"
