Re: Procedure names vs. production support

On Thu, 2005-02-17 at 23:05, Paul Morgan wrote:
> Rick,
> 
> How about another option?  Use descriptive names in your prototype like
> option 1 but use source member procedure names in the module like option 2.
> Use the EXTPROC keyword on the prototype to link the two together.  When a
> runtime error occurs they will see the source member procedure name in the
> error message.  For your example the prototype would look like:
> 
> D WritePaymentRecord... // why abbreviate when you don't have to?
> D                       PR                    EXTPROC('SP4351M')

I basically do this in RPGNext.  I call it "Dual Prototyping", it's one
of my favorite techniques.

I wrote an article about it here:
http://www.midrangeserver.com/fhg/fhg051204-story03.html

Joel Cochran
http://www.rpgnext.com