|
Thanks David. But why does the one program that has the procedure interface also need the prototype? In fact, why call it two different things at all? My first thought when I saw all that was why doesn't the compiler simply look at the called program to determine the prototype (after all, I don't have to have a prototype for a BIF, and I'd prefer some sort of external definition) but I suppose it keeps the compiler simpler and helps the programmer to see it documented. A problem with using /COPY's to define prototypes is that there is no reference in the program indicating which version of the /COPY was used when the program was compiled. Which is one of the nice things about externally-defined files. ----- Original Message ----- From: David Gibbs <david@midrange.com> To: <RPG400-L@midrange.com> Sent: Friday, September 24, 1999 12:38 PM Subject: Re: RPG IV program - comments requested > > Can someone please explain why the repetition between the prototype and > > procedure interface? The ILE RPG manual has the following definitions: > > > > "A prototype is a definition of the call interface." > > Which tells other programs how to call the program. > > > "A procedure interface definition is a repeat of the prototype information > > within the definition of a procedure." > > Which tells the program how other programs will call it. > > Basicly, many programs will use the prototype (which is why it should > be in a /copy member)... but only one program will use the procedure > interface. > > david > > > +--- > | 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 > +--- _________________________________________________________ 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.