Path: utzoo!news-server.csri.toronto.edu!rutgers!uwm.edu!cs.utexas.edu!uunet!hsi!stpstn!cox From: cox@stpstn.UUCP (Brad Cox) Newsgroups: comp.lang.c++ Subject: Re: Static typing, OOP efficiency, and programmer error Message-ID: <6648@stpstn.UUCP> Date: 11 Mar 91 20:51:10 GMT References: <27C523A2.2155@tct.uucp> <27CE9C05.4F64@tct.uucp> <1861@news.tcs.com> Reply-To: cox@stpstn.UUCP (Brad Cox) Organization: Stepstone Lines: 39 In article <1861@news.tcs.com> gwu@nujoizey.tcs.com (George Wu) writes: >always better to get as much error checking done at the compile stage. The >mere potential for run-time errors implies more testing and less overall >confidence in the stability of an application, to be avoided where possible >for commercially delivered applications. I heard this so often that I suppose you must all be right. All right, you win, you win! I surrender. I'll embrace fabrication-time binding and forget about dynamic assembly of pre-fabricated off-the-shelf components, where the only type safety is provided by us dumb old fallible humans. I'll have the dynamic binding on my ski boots welded to remove any possibility of run-time errors. Or better yet, since I might forget to close the boot snaps, or even wear the wrong boots. How'd we apply compile-time binding strong type-checking, and inheritance latices to that? I know! Fabrication-time binding...at conception time! No more ski binding errors! (Of course, my reusability for other than skiing would suffer... but won't the strong type-checking be wonderful! I'll only buy electronics that are completely wafer scale integration, to remove any possibility of assembly-time misconnections. Can anybody recommend a good place to buy wafer-scale CD players; wafer-scale hi-fi sets, cars, and living rooms? A wafer-scale universe? I'll only fly on airplanes that were cast as a unit from a mold, since assembly-time binding might cause core dumps (or worse ;-) ) No sirree, none of that bad old dynamic assembly-time binding for me. I'm going to settle on fabrication technologies where the parts and the whole come into existence simultaneously, to make dynamic (assembly-time) binding errors will be a thing of the past. Anyone else want to join me in this perfectly type-safe world? -- Brad Cox; cox@stepstone.com; CI$ 71230,647; 203 426 1875 The Stepstone Corporation; 75 Glen Road; Sandy Hook CT 06482