Yeah I'm referring to the WDSCi outline. It has made me lazy. :)
Actually, the reason why I prefer it over ctl-F is because I can click
on it and it takes me to the procedure. Let's say that procedure is
called 15 times within the module (maybe it's error-related) - ctl-F
takes too long. It's all perception and relative to how one works, but
I can generally see most, if not all, procedures at all times in the
outline, and that makes moving within the program lightning fast for me.
I suppose my use of the word "difficult" was going too far. It's simply
easier for me to navigate via the outline than to do ctl-F (because the
first, second, maybe even fifth search might not get me to where I want
to go, and I could have already clicked on the outline to be where I
want to be).
I appreciate the responses. It's good to hear how and why people do
things differently.
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Adam Glauser
Sent: Thursday, November 13, 2008 8:29 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: How do you sequence/order your subroutines/subprocedures?
Kurt Anderson wrote:
I've always done it (subprocedures, I don't do much with subroutines)
alphabetically - mainly because the outline will not alphabetize them
-
and they're a pain to find otherwise. I believe the outline does
alphabetize subroutines (for whatever reason).
To which outline are you referring? The outline view of WDSC, or
something else? I'm a bit surprised by your comment about
non-alphabetized routines being difficult to find. Isn't that what find
functions are for? SEU, green screen debugger, LPEX and WDSC debugger
all have 'find this string in the source' tools.
I work similarly to Rory, in that I tend to put internal-only
subprocedures at the bottom of a source member, and for the same reason.
Within either group (exported or non-exported) I generally add new
subprocedures at the end of the group, unless they are closely related
to other existing subprocedures.
For example, if I had these subprocedures:
splitStringOnDelimiter()
rightJustifyString()
convertStringEncoding()
and I wanted to add a procedure to centre a string in a field, I'd add
it between rightJustifyString() and convertStringEncoding().
Hope this helps,
Adam
midrange.com
