Slime <fak### [at] emailaddress> wrote:
> > As I say, the trouble is that if your program doesn't work, there is no 
> > way you can ever find out why.

> Honestly, binary search with prints works in a lot of cases. If you know 
> what the program is supposed to do, then you can identify the places it does 
> something wrong.

  Often a good debugger is easier to use than having to write those prints.
(OTOH debugger breakpoints aren't always the solution either...)

-- 
                                                          - Warp

Post a reply to this message