Re: binding directories and procedure prototypes

Now that do-loops and named indicators have been beaten to death, how
about some discussion on the above.

What sort of standards are you establishing.  Do you put all modules in
a binding directory for an entire application and use it on all CRTPGM's
or do you create a separate one for each program?  If you include
service programs in your binding directory, do you also include the
modules that are in the service programs?

Do you put your procedure prototypes in a copy member and include that
in your programs?  Do you put all prototypes in one copy member or
separate ones?  Is there additional overhead for prototypes for
procedures that aren't actually used in a program or are they like
unreferenced fields?

-- 
Nelson Smith
Haines City, FL, USA
ncsmith@gate.net
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *