RE: Function Opinion

I have a question about testing with this method.  In our shop, if I have 
multiple procedures in a single source member that compiles into a module and I 
change one of the procedures or add a new procedure I will probably be required 
to test every procedure because the source changed.  How do you handle this?  
Can you get by with testing only the changed/added code?

Because of this testing requirement I lean toward making each procedure it's 
own module.


> -----Original Message-----
> From: Rich Duzenbury [mailto:rduz-midrange@xxxxxxxxxxxxxxxxxxx]
> Sent: Wednesday, October 15, 2003 6:25 PM
> To: RPG programming on the AS400 / iSeries
> Subject: Re: Function Opinion
> 
> 
> 
> 
> So for now, one or many functions go into one module, one 
> module goes into 
> one service program.  Each service program is added to one binding 
> directory.  Binding directory is referenced by each main 
> program.  It's 
> simplistic, but it gets the job done.  So far, most programs 
> open only a 
> few service programs, but I am concerned about the potential 
> performance hit.
> 
>