Re: Benefits of Sub-procedures

Here's my first balking point.  Why do I have trouble accepting the idea
that two new source members in two different files is simpler and clearer?  
Why aren't we putting everything but the main program into QBIGHONKIN?  Why
isn't there just one /COPY statement? 

 /COPY QBIGHONKIN,myfunc
 
or 

call (e)   'myfunc'         some_data
 

I believe I know the answer, but I also believe I am wrong.  
---------------------------------------------------------
Booth Martin   http://www.MartinVT.com
Booth@xxxxxxxxxxxx
---------------------------------------------------------
 
-------Original Message-------
 
From: RPG programming on the AS400 / iSeries
Date: Friday, October 24, 2003 8:49:44 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Benefits of Sub-procedures
 
... So, I'd
have 3 source members:
 
QRPGLESRC mainpgm
QRPGLESRC subprocedure
QPROTOSRC subprocedure
 
The main program would look something like this:
 
/copy qprotosrc,myfunc
*entry plist
....
eval answer=myfunc(some_data)
....
/copy qrpglesrc,myfunc
return
 
   --buck