× 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: RPG/400 pgm strange behavior
  • From: Joel Fritz <JFritz@xxxxxxxxxxxxxxxx>
  • Date: Thu, 13 Jul 2000 08:51:08 -0700

Seems to me that the binding process resolves external references by
searching for the identifier specified in the extproc or extpgm keyword on
the prototype.  I bet you could have the same library list problems as ever,
though.  Especially if you have a binding directory in your test library
that refers to objects different from the ones in the production binding
directory.

-----Original Message-----
From: Richard Jackson [mailto:richardjackson@richardjackson.net]
Sent: Wednesday, July 12, 2000 7:58 PM
To: RPG400-L@midrange.com
Subject: RE: RPG/400 pgm strange behavior


Are the RPG prototypes "externally described" or could I create a program
with a wrong prototype, compile it successfully, the run the program and
cause a failure?

Richard Jackson
mailto:richardjackson@richardjackson.net
www.richardjacksonltd.com
Voice: 1 (303) 808-8058
Fax:   1 (303) 663-4325

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


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.