|
> Also, I don't think it would be a good idea, if using the /COPY, to use external > definitions for the prototype, since another program that /COPYes the file in may > not use the same files, so won't have the definition for the variable. What I meant was, use an external definition of the prototype *other* than a /COPY. I suppose /COPY is an external definition. BTW, unless you specify the library and file on the /COPY, you could easily get an outdated version of the /COPY. If you're working on the calling program, which /COPY did the called program use? And vice versa. Ok, the prototype makes it simpler for the compiler to determine whether a particular call to the procedure is valid. So in the calling program you should use a prototype. Being lazy, I still feel the compiler should get this from the called program or procedure. And DSPPGM or DSPMOD should show it. However, in the called program or procedure, why is it necessary to put the prototype? Isn't all this information in the program interface? Another question to clarify my hazy understanding of these concepts - near as I can tell, a service program is similar to a DLL (dynamic link library). Is this true, or do they need to be bound to a program at compile time? And if they are bound at compile time, are only the called procedures within the service program bound, or the whole thing? _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.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.