Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site calgary.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!alberta!calgary!radford
From: radford@calgary.UUCP (Radford Neal)
Newsgroups: net.works
Subject: Finding multiple bugs in one pass
Message-ID: <997@calgary.UUCP>
Date: Tue, 26-Feb-85 17:03:08 EST
Article-I.D.: calgary.997
Posted: Tue Feb 26 17:03:08 1985
Date-Received: Fri, 1-Mar-85 07:54:28 EST
Organization: University of Calgary, Calgary, Alberta
Lines: 16

Would someone please explain what's so wrong with fixing only one bug
in a run? Seems to me it is good practice NOT to try to fix more than
one problem at a time. This avoids possible interactions which weren't
anticipated. 

Of course, if the compiler is slow you may be forced into making more
than one fix at a time, but it's still undesirable in itself.

I think what people are really trying to say is that programmers should
spend more time looking at, and understanding, their programs, rather
than mindlessly setting breakpoints. I can agree with this, but I'm not
convinced that interactive environments really encourage the opposite
among good programmers.

    Radford Neal
    The University of Calgary