Re: Binding directory question

Hi, David:

You probably should use a "naming convention" to avoid any possibility that two or more modules might contain procedures with the same names. For example, you could prefix the procedure names with (at least part of) the module name. You would need to do this initially for any cases where you happen to have procedures with the same names in two or more different modules, and you would need to change all of the programs that call those procedures, to use the new names, before you can successfully create "one big binding directory" and add all of the modules to it.
Hope that helps,

Mark S. Waterbury

> David FOXWELL wrote:

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.