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



If there were two different functions with identical names and (god forbid) identical parameters and the compile command stated to ignore duplicate name errors, would binding occur? Has anyone tried?

-----Message d'origine-----
De : rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] De la part de Buck
Envoyé : vendredi 23 janvier 2009 15:11
À : rpg400-l@xxxxxxxxxxxx
Objet : Re: Binding directory question

David FOXWELL wrote:

My question :
Given that we continue to bind exclusively by copy, what would happen if, instead of a BNDDIR for each program, we made one huge BNDDIR and shoved the whole lot of modules in it?
Does the compiler only use what it needs from the BNDDIR. Isn't it similar to having one PF as a data dictionary for using REFFLD in DDS?


BNDDIR is like a library list - the compiler will look through it to find procedure names that it needs.

The biggest danger is name clashes. Let's say you have a getName in your A/R module to get the company name. If you also have a getName in your A/P module to get the payee name (from a different file) then the compiler will not be able to tell which one any given program needs.

You may need a single source who controls procedure names.
--buck
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.