RE: Indicators

[Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>]

> This sounds like an area where there isn't a standard (or at least it
> isn't clear).  IMHO, the worst situation would be having a source member
> with both subroutines and sub-procedures in them.  While functional,
> this would be confusing.

You can have subroutines inside subprocedures... for example, to break
your subprocedure into smaller pieces.  Not something I recommend, mind
you, but it's possible.

The only exception, I guess, is *PSSR.  Each subprocedure can have it's
own *PSSR, too...  Useful for handling unexpected circumstances and
reporting them back to the programmers or other tech support staff...


> Since there is a difference of opinion, possible solutions might be:
> - if source has subroutines, continue to use subroutines
> - if source has sub-procedures, continue to use sub-procedures
> ** or **
> Perhaps an edict from the Standards-God to use one or the other?  It
> would seem logical that someone needs to make a decision at some point,
> or agree to disagree.


I don't really understand why anyone would prefer subroutines, aside from
the fact that it's what they're used to.

Really, a subprocedure is just a subroutine with additional (but optional)
capabilities.  Aside from parameters, local variables and the ability to
export them, they're the same thing as subroutines.

Why would you NOT want to be able to pass parameters and return values?
Worried your code might become TOO reusable?  I just don't get it.



> I have the distinct advantage of being the development team, so when I
> encounter a situation, I can make a decision and stick to it until I
> decide something else is better, at which point I make another decision.
> I have been in your situation as well and don't lightly make the "edict"
> case.  Sometimes, however, that is the only way...even if it isn't my
> method that is chosen.

An edict that doesn't allow people to grow into the future (or in the case
of subprocedures, to grow into the present day) is counter productive.

You never hear of things like this in Windows or Unix shops. Why is that?