Re: Standard source file names?

On 4/1/2015 1:35 PM, Dan wrote:

Seriously? Client-based development for i (RDi, WDSC, etc.) is, in my
experience, by far the exception rather than the rule. Even in 2015. I
agree with your assessment that RDi negates the "ease of navigation"
argument, but this is a habit from my pre-RDi days. Otherwise, why bother
with all of the different source files if (most) everything is using the
source type to determine what to do with it? I still prefer the
"enforcement" of unique names that using one source file enables.

Sharing a different perspective but first, geezer alert! I started in
this business when programs had 6 character names. My fossilised brain
really dislikes the notion of using any of the name characters as a
replicant of the object type, ie PGMNAMR, PGMNAMC, DSPFILD etc. even
though we have ten! character names now. I'm just plain unhappy to
sacrifice any of them. Additionally, I really like the fact that my
prototype, source, service program, and binder language all have the
exact same source member name. It makes it very easy to find all the
pieces / parts of an ILE service program. So that's why I personally
use multiple source files.

On Wed, Apr 1, 2015 at 12:51 PM, Mark Murphy/STAR BASE Consulting Inc. <
mmurphy@xxxxxxxxxxxxxxx> wrote:

It is amazing the number of "ease of navigation" arguments that are still
being used as RDi removes them by allowing you to open any source in any
source file with the same number of key strokes, or by grouping them
together in a common filter. I know a lot of folks are still on an old
release, but how many are using SEU with v7.1 or v7.2? There are a lot of
new features which are unavailable to you under SEU, at least if you want
SEU to provide even the minimal assistance it has in the past.

Continuing the sharing (it's not an argument because I don't disagree
even though I am... different!) I never personally experienced
navigation issues between source files because I always ran multiple
5250 sessions. One WRKMBRPDM QCLSRC, one to WRKMBRPDM QRPGSRC and so
on. If, for some reason I needed to 'jump around' a QDDSSRC file, I'd
open another 5250 session to look / work with the needed source member.
Alt-tab was a very natural way to navigate the mental map of what was
where - in fact, it took some mental work to start using Ctrl-F6 in RDi.