Xref: utzoo comp.object:424 comp.lang.c++:5546
Path: utzoo!utgpu!watmath!att!rutgers!ucsd!usc!apple!sun-barr!decwrl!shelby!csli!keith
From: keith@csli.Stanford.EDU (Keith Nishihara)
Newsgroups: comp.object,comp.lang.c++
Subject: Re^2: Understanding the Object-Oriented Life-Cycle
Message-ID: <11074@csli.Stanford.EDU>
Date: 17 Nov 89 02:03:21 GMT
References: <20481@brunix.UUCP> <5026@internal.Apple.COM> <315@shrike.AUSTIN.LOCKHEED.COM> <654@nastar.UUCP> <44454@sgi.sgi.com> <1403@odin.SGI.COM>
Sender: keith@csli.Stanford.EDU (Keith Nishihara)
Reply-To: Neil%teleos.com@ai.sri.com
Followup-To: comp.object
Organization: Center for the Study of Language and Information, Stanford U.
Lines: 11

thant@horus.sgi.com (Thant Tessman) writes:
>... What 
>does the program written in a dynamic typing language do when the type 
>is wrong that you couldn't get a c++ program to do just as easily?)

Generate run time errors.

Not that you couldn't get C++ to generate run time errors, but you might
have to try hard to get it not to generate compile time errors first.

Neil/.		Neil%teleos.com@ai.sri.com	...decwrl!argosy!teleos!neil