Add initial stab at scoping the debugger issue...
Running jsexec with the -D argument will enter the debugger. Inside the debugger, there are the following commands: "r" runs the script "clear" clears any pending exceptions (mostly useless) "break ###" set a break at the specified line number "e <statement>" eval()uates <statement> in the current frame "eval <statement>" also eval()s This is a proof of concept right now since it's only in jsexec and the command parser is a joke. Eventually, this will also work for ;EXEC scripts in the BBS and be even more awesome. This should be enough to get mcmlxxix off my back though.
Please register or sign in to comment