Debugger Enhancement
Forum rules
This forum is for discussing APL-related issues. If you think that the subject is off-topic, then the Chat forum is probably a better place for your thoughts !
This forum is for discussing APL-related issues. If you think that the subject is off-topic, then the Chat forum is probably a better place for your thoughts !
Debugger Enhancement
I frequently find myself going back several lines of code in the debugger as I am developing, executing, fixing code. Currently I have to click on the << key many times. It gets tiring very soon. There should be a way to either drag the line of execution or ability to jump back to a particular line in the debugger. Does this already exist?
Re: Debugger Enhancement
Hi,
I don't know if this will help but I often find myself in the same situation and I use the keyboard shortcut Ctrl-Shift-Backspace to go back one line instead of using the button.
The difference here is that you can go back quickly to a previous line by holding down the key, something you cannot do with the button.
/Dan
I don't know if this will help but I often find myself in the same situation and I use the keyboard shortcut Ctrl-Shift-Backspace to go back one line instead of using the button.
The difference here is that you can go back quickly to a previous line by holding down the key, something you cannot do with the button.
/Dan
Re: Debugger Enhancement
Thanks Dan, that will make it easier, but the request still stands. This would be a very useful enhancement. The Dyalog debugger is used not just for debugging but for development as well!!!
-
- Posts: 439
- Joined: Wed Oct 01, 2008 9:39 am
Re: Debugger Enhancement
Hi Neeraj,
I've logged this request in our Request for Enhancement (RFE) database.
Regards,
Vince
I've logged this request in our Request for Enhancement (RFE) database.
Regards,
Vince
- Dick Bowman
- Posts: 235
- Joined: Thu Jun 18, 2009 4:55 pm
- Contact:
Re: Debugger Enhancement
Can I suggest another possible enhancement - or give someone the chance to tell me that it's already done?
I'd like to be able to make stops "present but inactive". What I'm thinking about here is that sometimes I want to put a whole lot of stops into some code (many functions/operators) so that I can review/revise. Which means that I have a functioning application (code-in-workspace) which is going to do a lot of stopping as it runs - which is inconvenient if I want to defer my code review and just run it as-is.
Wiping all the stops is too brutal (that session option really needs a "do you really want to?" prompt before it wipes everything out) - what I want to do is leave a marker that says "stop here if stopping is turned on".
Does that make sense?
I'd like to be able to make stops "present but inactive". What I'm thinking about here is that sometimes I want to put a whole lot of stops into some code (many functions/operators) so that I can review/revise. Which means that I have a functioning application (code-in-workspace) which is going to do a lot of stopping as it runs - which is inconvenient if I want to defer my code review and just run it as-is.
Wiping all the stops is too brutal (that session option really needs a "do you really want to?" prompt before it wipes everything out) - what I want to do is leave a marker that says "stop here if stopping is turned on".
Does that make sense?
Visit http://apl.dickbowman.com to read more from Dick Bowman
Re: Debugger Enhancement
That is akin to the directive "##if _DEBUG_" in C/C++ (not sure of the exact syntax)