The new code is in debugCommands.py so that you can follow along if you 
like. The changes from yesterday:

1. g.app.debugger_d is a dict containing all debugger data.

It does not exist until the user executes the xpdb command.

Only the debugger thread *sets *this data, which is good because otherwise 
it would have to be protected with some kind of lock.

2. Requests on the qr "channel" (queue) are now arrays of items.

The valid items are: ['stop-timer'] and ['select-line', line_number, 
file_name].  This is the "request protocol".

BTW, the "command protocol" merely consists of pdb commands.

3. The new xpdb.kill method stops the listener's timer and clears 
g.app.debugger_d ['xpdb'].

This is called when the user executes either the 'c' or 'quit' commands.

4. The db-input command issues a message if the debugger is not running.

5. The timer now explicitly runs at idle time, with a delay of 0.

6. The new 'xpdb-kill' command executes the debugger's 'quit' command.

*To do*

As stated yesterday, the 'select-line' request should actually cause Leo to 
select the proper line.

The xpdb command should prompt for a *file* (or maybe @file node) to run as 
the program under test.  For now, this is a low priority.

Edward

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Reply via email to