Thanks! This is brilliant. I didn't know about
h2xs -AXc -n, so that itself is a great tip. The only issue I have with your approach is that Foo and Bar are inherited from Foobar, which works against the mental model I had of this. In my mental model, Foobar was inherited from Foo as well as from Bar. As
JavaFan termed it, it was multiple inheritance I was after. Your approach requires in foo.pl
use FooBar::Foo.pm
use FooBar::Bar.pm
I want the user to be shielded from the inner workings of Foobar. So, as far as the user is concerned, only the following should be required in foo.pl
use Foobar;
That way I can add more "parents" to Foobar in the future, if required. For example, I could modify Foobar to inherit from Baz.pm as well, but the user would not have to change foo.pl.
All that said, many thanks for your very clear explanation.
--
when small people start casting long shadows, it is time to go to bed
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.