in reply to Relationship between directories and inheritance

From my point of view, you have some good reasons for the described structure of perl MODULES. It is ok. My strategy in the very similar cases is to keep my modules in some special directory, for instance, myperlmodules, which is NOT part of 'www'. In 'www' I have only small perl scripts, which do something as
use lib "/whenever/i/have/myperlmodules";
use App::Admin::Super;

App::Admin::Super::somemethod();

[download]

Replies are listed 'Best First'.
Re^2: Relationship between directories and inheritance
by philcrow (Priest) on Nov 13, 2006 at 17:05 UTC
    We take this a step further and build the modules as if they were for CPAN release, then inject them into our private CPAN mirror and install them as regular modules. No use libs are then required. This also urges us to build the dists professionally, ie with manifests, tests, etc.

    As for inheritence, if one module needs to inherit from a parent, a simple 

    use base 'Parent';

    [download]
    is usually enough.

    Phil

[reply]
[d/l]

In Section Seekers of Perl Wisdom