RE: Benefits of Sub-procedures

["Bob cozzi" <cozzi@xxxxxxxxx>]

For the same reason that when you go out to eat at a buffet, they don't put
all the food on the same serving try... because it makes you sick to look at
it and kills your appetite.  

Bob Cozzi
Cozzi Consulting
www.rpgiv.com


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Booth Martin
Sent: Friday, October 24, 2003 9:42 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: 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
_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.