From 4318658855470946268
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f78e5,ccbfcafab96cf493
X-Google-Attributes: gidf78e5,public
X-Google-ArrivalTime: 2001-12-09 11:16:01 PST
Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!dispose.news.demon.net!news.demon.co.uk!demon!mail2news.demon.co.uk!not-for-mail
From: "James Kuyper Jr." <kuyper@wizard.net>
Newsgroups: comp.std.c++
Subject: Re: Proposol to increase robustness of programs
Date: Sun,  9 Dec 2001 19:15:24 GMT
Organization: Posted via Supernews, http://www.supernews.com
Approved: Fergus Henderson <fjh@cs.mu.oz.au>, moderator of comp.std.c++
Message-ID: <3C12ADFE.4F6138BA@wizard.net>
References: <3BFE97B3.91430FB1@wanadoo.fr> <T23N7.64$%j1.23498@news11-gui.server.ntli.net> <3C058126.36357A00@acm.org> <EKwN7.1910$V51.448065@news11-gui.server.ntli.net> <3C06A0CE.E91638E8@acm.org> <Tb5O7.940$003.235141@news11-gui.server.ntli.net> <3C0C1E25.1A0247AD@acm.org> <3C0D410B.7198B21D@wanadoo.fr> <3C0D4878.A86E882E@acm.org> <7dc3b1ea.0112060840.69c166cc@posting.google.com> <3C0FD9D7.8F1845C4@acm.org> <7dc3b1ea.0112070704.1d8ad50f@posting.google.com> <3C11055C.899A4886@acm.org> <7dc3b1ea.0112080650.4af0bc11@posting.google.com> <3C125900.53951788@acm.org>
X-Trace: mail2news.demon.co.uk 1007925333 mail2news:444 mail2news mail2news.demon.co.uk
X-Complaints-To: abuse@demon.net
X-Mail2News-Path: news.demon.net!mulga.cs.mu.oz.au
X-Authentication-Warning: mulga.cs.mu.OZ.AU: fjh set sender to devnull@stump.algebra.com using -f
X-Robomod: STUMP, ichudov@algebra.com (Igor Chudov)
X-Accept-Language: en
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 19
Xref: archiver1.google.com comp.std.c++:8567

Pete Becker wrote:
...
> Making it easy to detect some portion of a class of errors at
> compile-time encourages sloppiness: hack the code until it compiles,
> then declare it finished. What's needed is the discipline to trace the

Of course that's the wrong procedure. The proper procedure is "Hack the
code until it compiles, then start really testing it." Making it easy to
detect some portion of a class of errors at compile time serves to make
the first part of that process more effective. It doesn't eliminate the
need for the second part. It doesn't have to eliminate that need, in
order to be worthwhile.

---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.research.att.com/~austern/csc/faq.html                ]



