RE: Procedure names vs. production support

Rick,
What was option 2 again? I deleted the email.
If it was the 1 proc per source member/module rule--then all I can say is if
people think that's a good idea, then they are not up to the skill level to
be using procedures anyway. 
Now, this does not preclude you from occasionally having a procedure that is
the lone ranger within a module, it just means that having a rule that
requires that kind of thing is only due to lack of experience with this
stuff.

All this procedure talk reminds me of when color displays came out on the
System/38. Nobody had experience enough programming color so we had all
kinds of colorful displays created, lots of rules and controls put in place.
As we as a community gain experience with procedures and service programs,
the things that are obvious to others who have already been through it will
become apparent to most people.

On the other hand, if option 2 wasn't the one-proc to one-module thing,
forget everything I just said. :)
-Bob