home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ogicse!mintaka.lcs.mit.edu!ai-lab!life.ai.mit.edu!tmb
- From: tmb@arolla.idiap.ch (Thomas M. Breuel)
- Newsgroups: comp.lang.c++
- Subject: Re: feedback wanted on appropriate OOPL
- Message-ID: <TMB.93Jan10170408@arolla.idiap.ch>
- Date: 11 Jan 93 01:04:08 GMT
- Article-I.D.: arolla.TMB.93Jan10170408
- References: <1992Dec30.171527.3534@informix.com> <1992Dec28.173620.14793@microsoft.com>
- <1992Dec29.011354.5929@informix.com>
- <726278910snx@trmphrst.demon.co.uk> <rmartin.726674455@thor>
- Reply-To: tmb@idiap.ch
- Organization: IDIAP (Institut Dalle Molle d'Intelligence Artificielle
- Perceptive)
- Lines: 16
- NNTP-Posting-Host: arolla.idiap.ch
- In-reply-to: rmartin@thor.Rational.COM's message of Sun, 10 Jan 1993 14:00:55 GMT
-
- In article <rmartin.726674455@thor> rmartin@thor.Rational.COM (Bob Martin) writes:
-
- A language can have a significant impact, however, on quality,
- run-time efficiency and coding efficiency. C++ will certainly catch
- more programmer errors than stalk [Smalltalk], [...]
-
- It is only true to say that _at compile time_, C++ will catch more
- programmer errors than Smalltalk.
-
- If you take into account both compile time and runtime, Smalltalk will
- catch more "programmer errors" than C++: not only will Smalltalk catch
- all type errors, but also bad pointers, overflows, and array bounds
- violations, errors that go undetected in most C++ implementations and
- are not mandated to be detected by the C++ definition.
-
- Thomas.
-