Kent Johnson wrote:
> J.T. Hurley wrote:
>> On the debug control, what is the difference between "go," over," and "out?"
>
> What debug control are you using?
>
> Debuggers usually have three kinds of stepping. The names vary but the
> concepts are the same:
>
> step in - execute the next line
Kent: I'm using IDLE's built-in debugger.
Alan: I just tried it out, and you were spot-on.
Thank you both for your assistance. I think I've got the hang of it
now. It'll certainly speed me up now that I don't have to step through
each function.
Thanks again,
J.T.
___
"J.T. Hurley" <[EMAIL PROTECTED]> wrote
> On the debug control, what is the difference between "go," over,"
> and "out?"
Cabeat, I haven't checked, but from memory:
go = Run the program from the current point onwards
until you hit the next break point or until it ends.
over = step over the fu
J.T. Hurley wrote:
> On the debug control, what is the difference between "go," over," and "out?"
What debug control are you using?
Debuggers usually have three kinds of stepping. The names vary but the
concepts are the same:
step in - execute the next line of code; if it is a subroutine call,
On the debug control, what is the difference between "go," over," and "out?"
Thank you,
J.T.
___
Tutor maillist - Tutor@python.org
http://mail.python.org/mailman/listinfo/tutor
