home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c++
- Path: sparky!uunet!munnari.oz.au!yarrina.connect.com.au!medicus.promed.com.au!giles
- From: giles@promed.com.au (Giles Lean)
- Subject: Re: feedback wanted on appropriate OOPL
- Organization: Pro Medicus, Melbourne, Australia
- Date: Wed, 13 Jan 93 00:26:37 GMT
- Message-ID: <1993Jan13.002637.1794@promed.com.au>
- References: <1992Dec30.171527.3534@informix.com> <1992Dec28.173620.14793@microsoft.com> <1992Dec29.011354.5929@informix.com> <726278910snx@trmphrst.demon.co.uk> <rmartin.726674455@thor> <TMB.93Jan10170408@arolla.idiap.ch> <rmartin.726795186@thor>
- Lines: 11
-
- rmartin@thor.Rational.COM (Bob Martin) writes:
-
- >Deferring error detection to runtime is risky, since the error may be
- >encountered several months after its release.
-
- ... and can result in phone calls to the developers! I want as much
- as possible to be caught at compile time. Nice runtime errors just
- makes the "it fell over/doesn't work" call somewhat more useful as
- a bug report.
- --
- Giles Lean at Pro Medicus <giles@promed.com.au>
-