|
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
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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
