|
Jim, While I break up my procedures themselves into subject-related service programs (like your math procedures), I have found it simpler to just put all the prototypes into a singe copy member (called Prototypes, strangely enough) and then just use the Define and Undefine compiler directives to include only the prototypes desired in any one given program. If you use a procedure in the program and forget to include the compiler directive for it, the compile listing will give you a 7030 error and you will see your mistake quickly. Also, all those service programs are listed in the same binding directory, so there is only one thing you have to remember on the compile commands, too. I believe in keeping it as simple as possible. ----- Original Message ----- From: "Jim Langston" <jlangston@conexfreight.com> To: <RPG400-L@midrange.com> Sent: Thursday, February 10, 2000 1:33 PM Subject: Prototypes and /COPYing > I have just started to use external calls and have a question, > how much overhead does a prototype bring to a program? What > I am contemplating is building header files similar to C files. One > I would call MATH_H. That would include atof, atoi, atol and those > types. Then, whenever I needed to use one of these I would just > /COPY the MATH_H into my program and be done with it. This > is basically what C does. > > Does anyone have any reason this would NOT be a good idea? > > Regards, > > Jim Langston > > +--- > | This is the RPG/400 Mailing List! > | To submit a new message, send your mail to RPG400-L@midrange.com. > | To subscribe to this list send email to RPG400-L-SUB@midrange.com. > | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- > +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
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.