Turbo Pascal 5.0
Is important to note how MUCH better some debuggers are than others. Pascal was amazing, specially if you compare to C.
Good debuggers:
- Pascal
- Delphi
- FoxPro /VisualFoxPro (the best of all, IMHO)
Others more common debuggers (Visual Studio, Xcode, IntelliJ, maybe others I don't remember), have issues, like the amazing "feature" of show opaque values, not allow to inspect stuff or requiere extra steps.
But the worse of all? Them are SLOW. Do "step" is slow. Waiting to see if evaluating values? slow.
Python have almost good, but mostly because python allow to see a lot. GDB sucks as is, but python make it look good.
Comments
Good debuggers:
- Pascal - Delphi - FoxPro /VisualFoxPro (the best of all, IMHO)
Others more common debuggers (Visual Studio, Xcode, IntelliJ, maybe others I don't remember), have issues, like the amazing "feature" of show opaque values, not allow to inspect stuff or requiere extra steps.
But the worse of all? Them are SLOW. Do "step" is slow. Waiting to see if evaluating values? slow.
Python have almost good, but mostly because python allow to see a lot. GDB sucks as is, but python make it look good.
Step being slow? How long you don't use debuggers?
Plus it is not like one needs to single step all the way, there are plenty of ways to control execution flow.
Stepping can be slow if you setup a lot of watches that get evaluated every time
That is what trace points like IntelliTrace are for, no need to single step.
Like 7h ago?
Then what about learning their advanced features for tracing and scripting instead of always single stepping?
That is a snarky way to answer.
But here, I was talking how other debugger have not the same problems.