Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!snorkelwacker.mit.edu!hsdndev!cmcl2!kramden.acf.nyu.edu!brnstnd
From: brnstnd@kramden.acf.nyu.edu (Dan Bernstein)
Newsgroups: comp.lang.misc
Subject: Re: Dynamic typing (part 3)
Message-ID: <18197:Mar1421:47:0991@kramden.acf.nyu.edu>
Date: 14 Mar 91 21:47:09 GMT
References: <609@optima.cs.arizona.edu> <25381:Mar1221:07:3891@kramden.acf.nyu.edu> <1991Mar13.124811.1380@newcastle.ac.uk>
Organization: IR
Lines: 14

In article <1991Mar13.124811.1380@newcastle.ac.uk> Chris.Holt@newcastle.ac.uk (Chris Holt) writes:
> So in prototype-style code, leave declarations out, and in production
> code put them in.

Well, I usually start writing a program by seeing how the data will be
organized. Once I know this, I might as well tell the computer about it.
(This is an observation about my programming style, nothing more; I
never decided that---what do they call it now?---``data structure
design'' was the Right Way to Code, and I can't argue that it's better
or worse than any other style.) What would I gain from pushing off
explicit declarations until the last moment? Are you saying that it's
not important to catch typos and type errors during debugging?

---Dan