|
Peter, The compiled library/object we are linking to does not contain prototype information, I don't believe. That is located in the source file for the library we built (I'm using Library as a term for the bound directory, I think, not sure what they are called). So, the compiler would not only have to find the bound directory object, but then it would have to find the source code, if you have it. If you didn't get the bound directory from another place that didn't supply you with the source code. In that case, it would be impossible without the source code. Regards, Jim Langston Peter Dow wrote: > Hi Paul, > > Are you saying it's impossible or merely difficult for the compiler to go > find a version of the service program in the library list and check its > procedure interface? > > Peter Dow > Dow Software Services, Inc. > 909 425-0194 voice > 909 425-0196 fax > > ----- Original Message ----- > From: Paul Tuohy <tuohyp@attglobal.net> > To: <MIDRANGE-L@midrange.com> > Sent: Sunday, February 13, 2000 1:42 AM > Subject: Re: Prototype in RPG/ILE > > > Hi Peter, > > > > This would be true if the procedure was coded in the same module. But > since the > > procedure could be coded in a module in a service program, the compiler > > (CRTRPGMOD) won't find the definition of the procedure. > > > > Paul Tuohy > > > > Peter Dow wrote: > > > > > Which tells me that "technically" a prototype is _not_ required, it just > > > makes it easier to write the compiler. A multi-pass compiler could > simply > > > flag the point where it found the function|procedure call, keep going > until > > > it found the definition of the procedure, which includes the procedure > > > interface which has the same information as the prototype. It could then > go > > > back and insert the code for the function|procedure call and make sure > it's > > > being called with the correct parameters. > > > > > > From: Jim Langston <jlangston@conexfreight.com> > > > > Answer: The compiler requires it to compile. > > > <big snip> > > > > +--- > > | This is the Midrange System Mailing List! > > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > > | To unsubscribe from this list send email to > MIDRANGE-L-UNSUB@midrange.com. > > | Questions should be directed to the list owner/operator: > david@midrange.com > > +--- > > __________________________________________________ > Do You Yahoo!? > Talk to your friends online with Yahoo! Messenger. > http://im.yahoo.com > > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-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.