On Jan 20, 2007, at 3:39 PM, johnf wrote:
> I don't know never used it the past. I just didn't like dabo.trace
> () very
> much.
That's just pdb. Guess you haven't done a lot of debugging in the
terminal, huh?
> I was hoping winpdb might work and saw your post. Now that it's at
> version 1.0.8 it might deserve a review. I'm still hoping for
> something that
> will be simple and visual to debug a running cdxml file. You might
> also want
> to review pydb.
It works a lot like VFP's debugger, but because it's external and
highly GUI-fied, it's really pretty slow. Or at least it was when I
played with it. I never figured out exactly how to set breaks in code
ahead of time, either, like you can with VFP's SUSPEND or SET STEP ON.
pdb, and, by extension, Dabo's trace() function, is like most
command-line interfaces: intimidating to the new user and not
immediately intuitive without documentation. Once you get familiar
with the commands and how they work, though, it's a whole lot faster.
I can usually step through the code and find the problem using pdb in
the time it would take to launch winpdb.
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
