The point people are trying to make is that the file naming specifies nothing about the relationship between the classes.

These file layouts are all valid:

A.pm
B.pm

A.pm
A/B.pm

B.pm
B/A.pm

AB/A.pm
AB/B.pm

Foo/A.pm
Foo/Bar/B.pm

[download]

It's what's inside the files that determines inheritance, not the names of the files themselves.

Include the following before you use any of your private modules:

BEGIN { push(@INC, $ENV{'HOME'} . '/lib'); }

[download]

So, for example:

#!/usr/bin/perl

use strict;
use warnings;

BEGIN { push(@INC, $ENV{'HOME'} . '/lib'); }

use Foo::A;
use Foo::Bar::B;

my $a = Foo::A->new();
my $b = Foo::Bar::B->new();

[download]

In reply to Re^2: children without inheritance by tod222
in thread children without inheritance by anonymized user 468275

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.