× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Prototype in RPG/ILE
  • From: boldt@xxxxxxxxxx
  • Date: Tue, 15 Feb 2000 10:50:51 -0500



Peter wrote:
>Aha! So in fact the compiler _is_ already going out and finding the
>procedure interface whereever it may be in order to compare it to the
>prototypes? I had the impression it was simply using the prototypes to
>verify the procedure call parameters without having to find the procedure
>interfaces, saving a lot of hunting for the PI specs.

Huh?  Where did you get that idea from what I wrote?

A module that exports a procedure needs both PR (prototype) and
PI (interface) specs.  Normally, the PI is specified in the
source file as part of the procedure and the PR is specified in
a /COPY member included using a /COPY spec in the modules source.
The compiler does not hunt around looking for things - the
programmer needs to explicitly specify these things.

On the other hand, a module that uses a particular procedure
needs just the PR specs.  It gets them by including the /COPY
member that contains them.

Cheers!  Hans

Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.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 thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.