"Abstract classes and Perl" just makes me chuckle. Like you said, abstract classes allow you to define an interface... And in Perl, that comes down to precisely "a few method names". Despite there being at least two implementations (metioned above by tilly) of abstract classes in Perl, I can't help but wonder whether the minimal value is worth the effort.
Sure, using an abstract class in Perl prevents you from completely forgetting to implement one of the methods. It doesn't require that you even come close to using the same interface in the methods that share a name, because Perl has no useful, built-in tools for defining interfaces (prototypes are built-in but not useful for defining an interface and there are some modules that help you define an interface but they aren't built-in).
Now, if your interface was defined via something like Class::Contract, then an abstract class might be a worthwhile thing.
- tye (but my friends call me "Tye")In reply to (tye)Re: Why do you need abstract classes in Perl?
by tye
in thread Why do you need abstract classes in Perl?
by jeffa
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |