[sevensor]

Different benefits come from each approach. Printing stuff out means you get a record of what happened during program execution, which you can compare to what you expect to have happened. With breakpoints, you have to keep track in your head, not only of where you are, but of where you expect to be. They can be useful too, but I probably use print statements about ten times as often.

[tenken]

> With breakpoints, you have to keep track in your head, not only of where you are, but of where you expect to be. They can be useful too, but I probably use print statements about ten times as often.

Thanks for putting this so clearly. That is the headache with breakpoints in complicated systems with lots of layers of indirection.