🚀 go-pugleaf

In article <dewar.814190504@schonberg>, dewar@cs.nyu.edu (Robert Dewar) writes:
|> Ian says:
|> 
|> "Besides, an interactive debugger is essential in the real world."
|> 
|> Well in one sense this is true, namely the commercial sense. Since so many
|> programmers are lost without an interactive debugger, it is certainly true
|> that a compiler must have a debugger to be generally used.
|> 
|> However, the idea that it is impossible to write code without an interactive
|> debugger is rubbish. Indeed, using the clean-room approach, it is quite
|> practical to write code under conditions where the devlopers do not test
|> the code they write AT ALL, let alone fiddle around with interactive
|> debuggers.

May be it's just me then :-)

Seriously, though, I do find that using a debugger is the only way to start
pinning down what is going on with complex system calls, across a client-
server link. If something goes wrong, sometimes you don't even know
whether it was the client or the server that had a problem.

For example, try fixing OLE code that doesn't work without a debugger...

Ian