Why is a superset of functionality not implementing the subset in "any meaningful way"?
I do agree that doing this sort of thing is asking for trouble and not a "clean" way of going about things; your statement struck me as dogmatic, however.
Matt
P.S. See Tracking Inheritance Directly due to Hybrid Methods and On Sinning and Subclassing Recalcitrant Modules for some details on my recent adventures with Time::Piece for more information on this very topic. All the trouble sources from having a constructor acting either procedurally or as a method; the problems could be avoided by isolating the procedural aspects:
sub constructor { my $thing = shift; my $class = ref $thing || $thing; bless {}, $class; } sub factory_proc { __PACKAGE__->constructor(@_); }
In reply to Re: Re: Methods supporting both package and OOP style calls
by mojotoad
in thread Methods supporting both package and OOP style calls
by jk2addict
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |