Xref: utzoo comp.lang.c++:12382 comp.lang.objective-c:207 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!daver!tscs!tct!chip From: chip@tct.uucp (Chip Salzenberg) Newsgroups: comp.lang.c++,comp.lang.objective-c Subject: Re: Static typing, OOP efficiency, and programmer error Message-ID: <27E8E207.2DBE@tct.uucp> Date: 21 Mar 91 16:40:39 GMT References: <6648@stpstn.UUCP> <27E1806B.728B@tct.uucp> <1991Mar19.172652.6290@netcom.COM> Organization: Teltronics/TCT, Sarasota, FL Lines: 16 According to rkitts@netcom.COM (Rick Kitts): >Before you say, "But C++ can't get an error because it can't find a method!", >please consider that Objective-C can't get an error because it inserted >a copy constructor under your nose which has an incorrect behavior. That each language has flaws is not contested by anyone here. To say, "So what if my language has problem X? Yours has problem Y!" is poor form at best, unless problems X and Y are somehow connected. Method lookup and copy constructors have nothing to do with each other. Let's concentrate on the subject at hand, shall we? -- Chip Salzenberg at Teltronics/TCT , "All this is conjecture of course, since I *only* post in the nude. Nothing comes between me and my t.b. Nothing." -- Bill Coderre