Re: sub classing best practice

In Class, I need:
sub subclass { my $self = shift; return Class::SubClass->new(%{$self}); }
[download]

In package Class, yes, but you can put that snippet, wrapped in a { package Class; ... }, into Class/SubClass.pm.

Comment on Re: sub classing best practice Select or Download Code

Replies are listed 'Best First'.
Re^2: sub classing best practice by cLive ;-) (Prior) on Dec 11, 2006 at 18:19 UTC
Interesting suggestion - but that just feels wrong to me. One class to one file - otherwise debugging becomes bizarre if there's an error. Imagine the confusion parsing X.pm looking for a method that's declared in X::Y.pm uder a package X declaration!	[reply]
Re^3: sub classing best practice by ysth (Canon) on Dec 12, 2006 at 05:36 UTC
No more wrong than having a method in X return a new X::Y object. So long as you stick to a consistent way to do your factory classes, I don't see a problem.	[reply]