Newsgroups: comp.object,comp.lang.beta,comp.lang.c++,comp.lang.eiffel,comp.lang.python,comp.lang.sather,comp.lang.smalltalk Path: news.daimi.aau.dk!news.uni-c.dk!sunic!sunic.sunet.se!newsfeed.tip.net!news.seinf.abb.se!eua.ericsson.se!cnn.exu.ericsson.se!convex!news.eng.convex.com!hermes.oc.com!news.unt.edu!cs.utexas.edu!swrinde!gatech!news.mathworks.com!zombie.ncsc.mil!paladin.american.edu!news.ecn.uoknor.edu!munnari.oz.au!cs.mu.OZ.AU!munta.cs.mu.OZ.AU!fjh From: fjh@munta.cs.mu.OZ.AU (Fergus Henderson) Subject: Re: Rapid Prototyping + statically-typed OOPLs? Message-ID: <9520601.9596@mulga.cs.mu.OZ.AU> Sender: news@cs.mu.OZ.AU (CS-Usenet) Organization: Computer Science, University of Melbourne, Australia References: <805548287snz@galacta.demon.co.uk> <3u13og$ehd@martha.utk.edu> Date: Mon, 24 Jul 1995 15:50:16 GMT Lines: 13 Xref: news.daimi.aau.dk comp.object:33984 comp.lang.beta:485 comp.lang.c++:130903 comp.lang.eiffel:9608 comp.lang.python:5173 comp.lang.sather:2010 comp.lang.smalltalk:24780 mbk@caffeine.engr.utk.edu (Matthew Kennel) writes: >The combination of system-wide bulletproof strong compile-time typing and >garbage collection helped make the transition go without many problems. I'll second this. In my experience strong static type-checking is invaluable when you are making major changes to a program. -- Fergus Henderson fjh@cs.mu.oz.au http://www.cs.mu.oz.au/~fjh PGP key fingerprint: 00 D7 A2 27 65 09 B6 AC 8B 3E 0F 01 E7 5D C4 3F