My mate Toby sent me this email:
I love RDI … But I do come across one issue that I’m sure you can sort out… using SEU if I wanted to find the start of a subroutine, I always made them # something like #Clr or #Bld etc. and there was only 1 place in the source where I could zero in on the actual routine because in the heading I always ‘# Clr’ as a comment and that little space meant I didn’t end up scanning 14 #clr executes etc. I scan in RDI and I get back a list of source number lines where this is found, I would prefer to jump to it opposed to looking at the browse results then key in the line number. So how do you do that then?Toby wafffling his version of technoburble
Scanning for Subroutines in RDi
Scanning for subroutines is easy with RDi.
It’s as simple as rebooting your brain out of the old SEU mindset.
Remember, SEU as like a really basic NOTEPAD editor and only has the most rudimentary functions.
To get around this limitations we used to formulate various techniques – the example you mention here “adding a comment with the subroutine name in it so I can jump to the comment using a SCAN statement, ignoring all the subroutine calls in the mainline” is just a workaround for SEU’s inability to show you where the subroutines live.
RDi does not have the limitations of SEU
In fact, RDi has a built in code overview which gives us this information, plus lots more.
Let’s look at the OUTLINE view in RDi: