Re^2: I don't think inheritance is essential

Personally, I can't think of a good reason not to use inheritance.

I can. It encourages code reuse along the wrong lines, caring more about position in an arbitrary (and quite possibly wrong hierarchy) than about the capabilities of the class.

That's why Perl 6 encourages the use of roles.

Comment on Re^2: I don't think inheritance is essential

Replies are listed 'Best First'.
Re^3: I don't think inheritance is essential by sri (Vicar) on Sep 02, 2005 at 00:05 UTC
Yes, multiple inheritance is quite lame for mixin style programming, but try to think a bit more abstract. The important part is that we use it in combination with NEXT for AOP like programming, think AspectJ without static trigger points! `package Foo; use base qw/Bar::Unicode Bar/; __PACKAGE__->prepare_parameters; package Bar; sub prepare_parameters { my $class = shift; # initialize parameters... } package Bar::Unicode; use NEXT; sub prepare_parameters { my $class = shift; # let parent initialize parameters $class->NEXT::prepare_parameters; # utf8 encode parameters... }` [download] Hope this makes it a bit clearer.	[reply] [d/l]

Replies are listed 'Best First'.

Re^3: I don't think inheritance is essential
by sri (Vicar) on Sep 02, 2005 at 00:05 UTC

package Foo;

use base qw/Bar::Unicode Bar/;

__PACKAGE__->prepare_parameters;


package Bar;

sub prepare_parameters {
    my $class = shift;

    # initialize parameters...
}


package Bar::Unicode;

use NEXT;

sub prepare_parameters {
    my $class = shift;

    # let parent initialize parameters
    $class->NEXT::prepare_parameters;

    # utf8 encode parameters...
}
[download]

[reply]
[d/l]