Perl classes work by what has been defined in the right package. By tradition you put one class per file, but Perl does nothing to enforce that tradition.
Looks like I learned something new again.
(But use won't work properly unless you do that, so it is a good tradition to follow.)
And that's probably why I was thinking the one class per package thing is required.
Also I note that your "preferred way to call constructors" comment is just cargo culting unless you can give some concrete reasons why that is preferred. I'm betting that you can't.
I used to know why :) As best as I remember it had something to do with inherited constructors not working properly. (But you're right, since I can't really remember why anymore it is a cargo-cult thing now.)
Also what is the reason that you're afraid of using unless?
I strongly dislike the action appearing before the condition. I find it to be a lot more prone to causing confusion (for me) and decreasing readability. (And yes I know there's plenty of people who argue it does exactly the opposite.)
In reply to Re^3: OO Perl: Nested classes question
by Crackers2
in thread OO Perl: Nested classes question
by TheMarty
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |