× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.