in reply to Same function multiples unknown modules

The usual way to have several implementations of a function is to place them in a package namespace. If the modules furnish an object constructor, calling the runonce() method will automatically select the correct one.

To call a non-method runonce() from a package, use the fully-qualified name, 

Package::Name::runonce();

[download]
To call once for each package loaded, you'll need to go through all the loaded packages and try each. Here's an unsophisticated way to do it, 
for (keys %INC) {
    s!/!::!g;
    s/\.pm$//;
    eval { $_::runonce() };
}

[download]
The eval is used to trap fatal errors from packages which don't define runonce().

After Compline,
Zaxo

Replies are listed 'Best First'.
Re^2: Same function multiples unknown modules
by Delusional (Beadle) on Sep 19, 2005 at 13:59 UTC
    Thanks. This looks promising. At the moment I have two subdirectories where these .pm files are: Main and Addins. What would need to be changed to use only these two subdirectories. Not the root driectory where the main script is located, or the perl root, only the two subdirectories?
[reply]

      At the top of the loop, the line, 

          next unless m/^Main|Addins/;

      [download]
      will restrict attention to those two top level namespaces.

      After Compline,
      Zaxo

[reply]
[d/l]
        Thanks again Zaxo,
        I ran a test using this, however, the $eval fails on me (in a browser I get Error 500)...

        I use logging in the scripting to catch errors as well as MySQL calls (and anything else I choose to log). The log shows the following when the script is executed:

        Sep 26, 2005 (10:49:52) : ERROR SITUATION: Interface Crash, error message:
        syntax error at Main/Menu.pm line 101, near "$_::runonce(" Compilation failed in require at d:\PROGRA~1\APACHE~1\apache\cgi-bin\intern2.cgi line 31.

        In the file Main/Menu.pm I have your code as:
        sub sub_menus {
  for (keys %INC) {
    next unless m/^Main|Addins/;
    s!/!::!g;
    s/\.pm$//;
    #print "<font face=\"Arial\" size=\"2\">$_<br></font>\n";
    eval { $_::runonce() };
  }
}

        [download]
        The function, runonce (sub runonce), is available in exactly one file. Perhaps I shouldn't use sub, rather someother addressing scheme that I'm unawear of?

        If I comment out the eval line and use the print line, execution runs clean (with the exception of runonce not running).

        I assume the problem lye with the logging I have to catch problems and log them:
        $SIG{__DIE__} = \&error_crash_trapper;
$SIG{__WARN__} = \&warn_crash_trapper;

        [download]
        Is there any other way to achieve this? Essentially I'm looking for simplicity and the use of a 'dummy' routine that doesn't rely on hard coded information which then allows for dynamic implementation.
[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom