×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
