Re: Unresolved References using Prototyped Functions & CallP -- RPG400-L

× 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.

> Because it wouldn't have been "wrong".  The actual name used on the proto
> would have been used as the procedure name instead of the normal RPG
method
> of simply uppercasing the module name.  Since the proto is used when
> compiling the module and when compiling the calling module the names would
> match - voila!  problem solved.

So in fact you are saying "Don't use EXTPROC", which has nothing to do with
whether the called procedure uses a procedure interface or not.

Joep Beckeringh



+---
| 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 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.