Xref: utzoo comp.object:3300 comp.lang.misc:7580 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!udel!ee.udel.edu From: new@ee.udel.edu (Darren New) Newsgroups: comp.object,comp.lang.misc Subject: Re: Run-time Type Errors in Smalltalk Message-ID: <51639@nigel.ee.udel.edu> Date: 23 Apr 91 16:41:18 GMT References: <3865@ssc-bee.ssc-vax.UUCP> <530@eiffel.UUCP> Sender: usenet@ee.udel.edu Followup-To: comp.object Organization: University of Delaware Lines: 17 Nntp-Posting-Host: estelle.ee.udel.edu In article <530@eiffel.UUCP> bertrand@eiffel.UUCP (Bertrand Meyer) writes: >I don't think anyone has shown a convincing counter-example - >something that could be expressed conveniently in a dynamically >typed language but not in a statically typed language. I think a "resource manager" is a good example. By this, I mean a module which accepts pairs either to be stored or retrieved. Presumedly, the one storing and the one retrieving need to know what the type is, but the resource manager need not. Sort of like an environment-variable list, except that the right-hand side is not restricted to single strings but rather can be any type in the language. - Darren -- --- Darren New --- Grad Student --- CIS --- Univ. of Delaware --- ----- Network Protocols, Graphics, Programming Languages, FDTs ----- +=+=+ My time is very valuable, but unfortunately only to me +=+=+ +=+ Nails work better than screws, when both are driven with screwdrivers +=+