I wasn't making any comments about overall bug fixing methodologies, or trying to advocate a particular development lifecycle approach, my point was specificly addressing this issue of fixing compile time bugs/errors/warnings.

If you try to fix to many at once, you run the risk of not realizing a later bug is caused by a former bug, and spend excessive ammounts of time debugging lines of code that have nothing wrong with them (thanx to your orriginal fix) In my opinion, unless you can tell from the error msg exactly what the problem is, it's not even worth the time/energy of jumping to the line# of the next error to see if it might be a differnet problem. That 0.5 second can be better spent recompiling, and thinking about important things, like what grass smells like

The worst situations I've ever seen are people who forgot that in fixing their first error, they may have added/removed a line from the code, invalidating the line number the compiler gave them for the rest of their errors.
(You could argue that you people can keep in mind when you make a change that affects line numbering -- but why should they have to?)