in reply to mod_perl namespace

I think that different naming is less painfull then fiddling modules, specially in the situation, when that modules are really different...

If they are your modules, my idea is to prepend namespaces unique by applications, to distinguish MyModule.pm, for instance,
...appX/perl-lib/APPX/MyModule.pm
...appY/perl-lib/APPY/MyModule.pm
-> from mod_perl perspective, you have two different modules, APPX::MyModule and APPY::MyModule
->contrary, shared modules can be located in ...appX/perl-lib directory.

Replies are listed 'Best First'.
Re^2: mod_perl namespace
by Burak (Chaplain) on Jul 03, 2007 at 12:37 UTC
    So, it looks like you have to require "the file" not use() the module to accomplish this. This looks impractical to me.
[reply]
      No. I assume that @INC contains both paths (.../applicationX/perl-lib, .../applicationY/perl-lib) and modules are used: 
      #for X application
use APPX::MyModule;

      [download]
[reply]
[d/l]
        ah, ok :)
[reply]

In Section Seekers of Perl Wisdom