672910f27b
I started from tabs that are not on the beginning of lines, and in several places I did further cleanings. If you're worried about knowing who wrote some code, for example, if you get to this commit in "git blame", then note that you can use the "-w" flag in many git commands to ignore whitespaces. For example, to see per-line authors, use "git blame -w <file>". Another example: to see the (*much* smaller) non-whitespace changes in this (or any other) commit, use "git log -p -w -1 <sha1>".
38 lines
1.5 KiB
Plaintext
38 lines
1.5 KiB
Plaintext
- Stack navigation from REPL
|
|
- Automated tests
|
|
- Trace by function name
|
|
|
|
CHANGES TO MAKE-----------------------------------------------------------------------------
|
|
Ability to add named anchors into code using Special menu in DRS -- use those anchors as tracepoints.
|
|
|
|
Demo monitoring DrRacket for Robby?
|
|
|
|
Bind Stop button to kill-all.
|
|
|
|
On the whole, I like the tool, although it'd be nice to have either
|
|
(a) an interactive pointy-clicky interface rather than figuring
|
|
out line/column co-ordinates, or
|
|
|
|
|
|
Re-direct, or at least prefix, program output from the client so that it can be distinguished from the script
|
|
|
|
Paramterize print-struct to #f for printing in the script
|
|
|
|
ERROR-CHECKING/HANDLING---------------------------------------------------------------------
|
|
|
|
* Make all exposed cells and evstreams read-only by lifting the identity function on them
|
|
|
|
* Turn script errors into syntax errors (i.e. what happens when you bind to variables that don't exist)
|
|
--take the syntax when the binding is made and save it in a hashtable
|
|
|
|
|
|
TESTING/CAPABILITIES------------------------------------------------------------------------
|
|
* Does user interaction work? Can we step through loops one line at a time waiting for input? GUIs?
|
|
|
|
* What kind of interface do we want to dig into frames
|
|
|
|
* What do we do about binding to a variable and following it EVERYWHERE it goes. Even if it is assigned to something else.
|
|
|
|
* Implement access to the result of ananonymous expression: here->(add1 2)
|
|
|#
|