Re: debugging with new variables (dictionary, hash, ...) [message #90023 is a reply to message #90020] |
Thu, 15 January 2015 06:07   |
Helder Marchetto
Messages: 520 Registered: November 2011
|
Senior Member |
|
|
Hi,
I just found that the following combination of F-keys works for my purpose:
F5 and then F7. This can be done from the command line as .step and .out.
Wayne: thanks for the tip.
I'm fine with this (two key strokes are for sure better than 90 and just a bit worse than 1), however, for consistency, it would be nice if these functions (hash, dictionary,...) would be implemented in the compiler in such a way that one cannot go into them (.step).
Thanks and sorry for bothering with what seems like a trivial issue, but has driven me mad (and eroded my F5 key down of ~1mm).
Cheers,
Helder
On Thursday, January 15, 2015 at 2:27:54 PM UTC+1, wlandsman wrote:
> On Wednesday, January 14, 2015 at 5:28:50 PM UTC-5, Helder wrote:
>
>> If you type .SO first, then it will (obviously) step over the line "print, retValue(...)". If you use F5 to step in (don't know what the command line option is), then you can't get out with .SO. With .OUT you go too far out!
>>
>> Thanks anyway,
>> Helder
>
> I don't understand this comment. .SO will *not* step over the line "print, retValue(...)". Stepover is perhaps an unfortunate name. It does not skip or "step over" any lines. It takes one step and *if* you enter another procedure in that step it continues until you return (e.g exit the HASH call). This appears to be exactly what you are asking for.
>
> As for .OUT you would use it once you step into the HASH routine to get out of the HASH routine in one keystroke. Of course, by using .SO you can avoid ever entering the hash routine in the first place.
|
|
|