Xref: utzoo comp.lang.misc:7315 comp.object:3068 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!deccrl!news.crl.dec.com!shlump.nac.dec.com!tkou02.enet.dec.com!jit345!diamond From: diamond@jit345.swstokyo.dec.com (Norman Diamond) Newsgroups: comp.lang.misc,comp.object Subject: Re: Run-time Type Errors in Smalltalk (was Re: blip (was...)) Message-ID: <1991Apr8.085602.5082@tkou02.enet.dec.com> Date: 8 Apr 91 08:56:02 GMT References: <3523:Mar1803:21:0591@kramden.acf.nyu.edu> <22032@yunexus.YorkU.CA> <14160@life.ai.mit.edu> <1991Mar25.201620.5839@cua.cary.ibm.com> <879@puck.mrcu> <887@puck.mrcu> Sender: usenet@tkou02.enet.dec.com (USENET News System) Reply-To: diamond@jit345.enet@tkou02.enet.dec.com (Norman Diamond) Organization: Digital Equipment Corporation Japan , Tokyo Lines: 18 In article olson@lear.juliet.ll.mit.edu ( Steve Olson) writes: >In my opinion, the biggest practical problem with dynamically typed languages >is that it is a pain in the butt to lug around the run time envirnoment. >To run a 1 page Common Lisp program on a UNIX system means I have to fire up a >multi-megabyte run time system which consumes vast amounts of core and virtual >memory. Yuk. Exactly. The multi-megabyte run time system provides the "message not understood" message and nice debugger instead of mystery core dump. The multi-megabyte run time system would be useful while developing programs in statically typed languages too, and then you'd never see the mystery core dump. Debates between static and dynamic typing should center on the advantages of programming in each kind of language, not on what can be done with multi-megabyte support packages. -- Norman Diamond diamond@tkov50.enet.dec.com If this were the company's opinion, I wouldn't be allowed to post it.